#sqlite
- The capacity check that let all nine throughNine writers hit one limited slot at the same moment and all nine got on. The capacity check ran for every one of them, the lock was the right lock, and a one-user test passes it every time.
- Case study: the Paul Newman CupA full walk-through of a small production Flask app: the operational problem, the architecture, the identity-versus-permission model, the database and deployment decisions, the failure scenarios, and what shipping it taught me.
- The SQLite trap caught me the same day I wrote about itI published a post warning that SQLite on an ephemeral filesystem silently loses your database. Hours later, my own app turned out to have been doing exactly that on every deploy.
- Running SQLite in production (yes, really)I deployed a Flask app to Railway with SQLite as the only database. Here is why that was the right call, and the five things that actually bite when you do it.