markusw

I am so tempted to benchmark some more… :D Would be great to get some numbers on this, super interesting.

Note: The last paragraph was about in production, not tests. :-)

Uuuuh, that looks super interesting! I hadn't heard of that. Thank you for sharing!

Yeah, basically the same here, except it's Caddy in front instead of Traefik.

So you do periodic backups, not incremental on every write or something (read replica-like)?

It's important to me to not lose any data once committed if at all possible.

(For testing, I've sped everything up by running migrations on `template1` and every test gets a random database name. Works wonders.)

Ah, I thought I recognized your username from a Github URL. :D Thank you for your contributions in the SQLite & Go space!

I had no idea that was possible. I'll keep that in mind if I need a similar workflow. DuckDB is awesome. :D

Oh, interesting! But that's more of a desktop application now, right? I was thinking of web servers when writing the article, but I can see how that's not totally clear. :-)

Yeah, totally agreed. I'll have to look into that. I've really enjoyed the stability of SQLite, down to the file format.

The biggest one is latency. Network latency will almost always be orders of magnitude bigger than I/O latency. There's a whole class of problems that goes away when latency becomes very small.

Interesting! I'm going to look into that. :-) Thank you for sharing.

While I really like DuckDB, I wouldn't use it for OLTP workloads.

I'm curious, when do you want to treat your Postgres like SQLite? :-) That's basically the opposite of what I was thinking of in the article.

On the other hand, and especially if migrating from SQLite, there's typically not _that_ much data. Even hundreds of GBs would probably be okay? Drives are so fast these days. Would be interesting to benchmark.

Yeah, that really is a great thing about SQLite.

I wonder whether packaging everything in Docker (including a specific Postgres container identified by hash or whatever) and deploying on the same architecture would solve this?

Hehe. Yes and no.

In the cloud, as you probably know, the usual way now is to spin up Postgres separately (RDS, Supabase, Planetscale, Crunchy Bridge, you name it). We've gotten so used to it that a different way of doing it is often not even considered.

But I think tooling has come a long way, and there have been a lot of learnings from the cloud, so it's time to swing the pendulum back and reconsider assumptions!

Indeed pondering! The dude here. I think writing a little piece like that often sparks some interesting discussions here and elsewhere. :-)

It's also used plenty in the cloud, for a variety of reasons. Check out the first linked article for something I wrote on that: https://www.maragu.dev/blog/go-and-sqlite-in-the-cloud

You can easily do consistent backup on live databases. There’s a backup command and API.

Thank you for answering. That's fair re. App Store rules. Feature flags FTW? :D

I was happy to see that FTS5 was always enabled as a compile-time option.

I've just tried it out, looks nice!

I've been using TablePlus a lot, but there are some SQLite-specific features I'd really like to have in an app:

- Foreign keys enabled by default, so I don't have to remember to enable that in every session.

- Support for loading extensions automatically. I'm using sqlite-vec for example. Right now, browsing virtual tables for that just doesn't show that much, and executing a query just results in "no such module: vec0"

I'll keep an eye on the project. :-)

Beautifully done, thank you for sharing. :-)

I wrote about this back in 2022, still applicable today: https://www.golang.dk/articles/benchmarking-sqlite-performan...

My pulse is still higher than usual. We just spent an hour on this. This is an art game. :D Thank you!

You’re missing MIDI controllers, of which there are plenty. :) Synth versions without the keys are often called “desktop versions”.

I build my frontends with HTML using gomponents. The jury’s still out about how far I can get with just Go while incorporating LLMs into my apps, but I’m optimistic!

Yep! "Boring tech" has basically become an established term at this point, I'm not going to change that.

It's okay, sometimes the discussions turn interesting and I learn something. And a lot of people get to read my article, and I hope their lives are enriched in a small but meaningful way.

I'm glad the approach works for you as well! :D It's fascinating to watch a statistical document completion model be able to do so much.

I do!

In the article, I mostly mean working with LLMs inside the applications I'm building, as opposed to as a tool as part of development. But I do both.

Right now, I'm trying out Zed, which supports multiple LLMs natively. Just today, I tried Zed + Ollama + Qwen 2.5 Coder 32B running locally, and it worked! Blows my mind that I can have GPT-4o-level assistance running on my laptop. :D