News for hackers. Stuff that matters.
Re:SQLite is all you need for durable workflows by pibaker on Friday May 29, 2026 @03:51PM (#48328309)
GP calls out concurrency as a weakness of SQLite. Most of the examples here don't experience the same load even a moderately sized web service experience day to day.

And no, being a part of the python standard library doesn't means it is being used by the average python user. These days I'd say at least half of them are just there for machine learning.

Re:SQLite is all you need for durable workflows by OutOfHere on Friday May 29, 2026 @06:16PM (#48330039)
SQLite is good for read-concurrency, not great for write-concurrency.
Re:SQLite is all you need for durable workflows by simonw on Friday May 29, 2026 @06:24PM (#48330112)
SQLite requires writes run sequentially. Most SQLite write operations take single digit milliseconds or even microseconds. If your writes are inexpensive (inserting or updating single small rows) you'll probably never even notice the queue.
Re:SQLite is all you need for durable workflows by zarzavat on Saturday May 30, 2026 @05:30AM (#48334351)
Exactly, people confuse "doesn't scale" with "is a bottleneck". There's many applications whereby hitting the limits of SQLite is either a physical impossibility, or implies that the application has achieved success such that replacing SQLite is the least of anyone's problems.

I visited a piano store once that was running everything off MS Access. If only they had switched to HA technologies, they would be able to sell millions of pianos a day!