lobste.rs is now running on SQLite Community site Lobsters has been planning a migration away from MariaDB since August 2018 - originally targeting PostgreSQL, but last year they decided to investigate SQLite instead. This weekend they completed the migration, and now consider it stable enough that it looks like this is the permanent architecture for the site going forward: SQLite seems to have passed with flying colors: cpu usage is down, memory usage is down, site seems to be snappier at le ✦ AI generated
The migration finished over the weekend and the site's operators now treat SQLite as the long-term backend.
Simon Willison: This weekend they completed the migration, and now consider it stable enough that it looks like this is the permanent architecture for the site going forward
provides context · 1supports · 1
The Lobsters community site had a multi-year plan to leave MariaDB, initially targeting PostgreSQL, but pivoted to SQLite last year.
Simon Willison: Community site Lobsters has been planning a migration away from MariaDB since August 2018 - originally targeting PostgreSQL, but last year they decided to investigate SQLite instead.
A Lobsters operator reports the SQLite switch cut resource usage and cost while improving perceived performance.
Lobsters site operator (quoted from migration thread): SQLite seems to have passed with flying colors: cpu usage is down, memory usage is down, site seems to be snappier at least for me, 1/2 the vps cost once mariadb vps is taken down
Willison frames the Lobsters migration as proof that single-server SQLite deployments remain viable and capable in 2026.
Simon Willison: This is a really useful case study, and a great reminder that you can get a whole lot done with a single server and SQLite in 2026.
supports · 1
Post-migration, Lobsters' entire Rails app and its ~3.8GB SQLite database run on one server.
Simon Willison: The Lobsters Rails application now runs on a single VPS, with a primary content SQLite database file that's around 3.8GB.
The migration's scope is documented in a large PR by Thomas Dziedzic that built on prior groundwork PRs.
Simon Willison: There are plenty more details in both the linked thread and this SQLite migration PR by Thomas Dziedzic, which added 735 lines and removed 593 lines across 30 commits and 188 files.