fractaledmind

7 ms·

1.
by fractaledmind 2y ago
Author here: these are my original speaker notes and slides stitched together for the talk that I gave at Rails World 2024 in Toronto at the end of September. There is a link to the YouTube video at the top of the post. Unfortunately, the v
2.
by fractaledmind 2y ago
Rails works with a connection pool and multiple threads processing incoming requests. Not a problem. In fact, Rails has one of the very best tunings to use SQLite in production in the context of a web application. And yes, you can also star
3.
by fractaledmind 2y ago
As I explain in the post, if you have multiple connections and consistent write load, the timeout will penalize older quereres and noticeably harm your long tail latency
4.
by fractaledmind 2y ago
Very true. There isn’t an actual limit. You can horizontally scale with SQLite if you want to or need to. I just think it is worth pushing vertical scaling as far as possible as long as possible. And I don’t actually believe that SQLite is
5.
by fractaledmind 2y ago
Not so fast https://github.com/rails/rails/pull/52889
6.
by fractaledmind 2y ago
This is my perspective as well. You certainly can horizontally scale with SQLite, but I strongly recommend that you vertically until you hit an actual limit there. If you know you will absolutely need multiple app nodes on day 1 or day 10,
7.
by fractaledmind 2y ago
I’m very excited that yes indeed we have the four major pillars in Rails 8, which is releasing soon, but can be used now via the main branch. The default, out-of-the-box experience with Rails 8 will go all in on SQLite, a database will be t
8.
by fractaledmind 2y ago
You can read more discussion here: https://github.com/sparklemotion/sqlite3-ruby/pull/528 and here: https://github.com/digital-fabric/extralite/pull/46 to see how it was valida
9.
by fractaledmind 2y ago
This presentation is focused on the use-case of vertically scaling a single server and driving everything through that app server, which is running SQLite embedded within your application process. This is the sweet-spot for SQLite applicati
10.
by fractaledmind 2y ago
Yep, that was an errant duplication. I did proofread, but how is it that one thing always seems to sneak through anyway? Thanks for the catch. Fixing now.
11.
by fractaledmind 2y ago
I've been using it for a couple different production apps, and it has been great. No problems for me.
12.
by fractaledmind 3y ago
I cannot believe how simple and elegant this is. Using an iframe as a request/response proxy to enable targeted replacement is just
13.
by fractaledmind 3y ago
This looks like it could be a big deal for Rails developers. Increased speed to build standard UI elements, completely control over the look and feel, plus increased rendering speed due to Phlex. I can only imagine how much time this has
14.
by fractaledmind 3y ago
Yes, the .sqlite file needs to be persisted across deployments. It is fairly common for the /storage directory to be persisted across deployments. The Kamal deployment tool will use this directory. The Hatchbox.io service likewise uses
15.
by fractaledmind 3y ago
When you open your database connection in WAL journal mode, you can have multiple concurrent readers. This is the new default for all Rails applications. WAL mode doesn’t allow concurrent writers, but you are often talking about millisecond
16.
Setting Up Litestream on Debian Linux with DigitalOcean Spaces(fractaledmind.github.io)
1 points by fractaledmind 3y ago|0 comments
17.
Loading SQLite Extensions in Rails(fractaledmind.github.io)
1 points by fractaledmind 3y ago|0 comments
18.
Fine-tune your SQLite database for production web app usage(fractaledmind.github.io)
4 points by fractaledmind 3y ago|0 comments
19.
PlanetScale-style database branching for Rails and SQLite with 2-lines of code(fractaledmind.github.io)
4 points by fractaledmind 3y ago|1 comments
20.
by fractaledmind 3y ago
The first time I read about PlanetScale's "database branching" feature, I felt the way one does when they realize something, but it feels like they always should have known it. Dealing with a single database schema for local