> And, finally: SQLite wants a single writer per database. But there's no rule that says your entire app has to land in a single .db file. I like finding hints

> And, finally: SQLite wants a single writer per database. But there's no rule that says your entire app has to land in a single .db file. I like finding hints of our architecture scattered across these SQLite threads :D It's very sketchy trying to slam all users into a single physical database. If you can slice up the users along unit of work, session, customer, account, etc., you can go horizontal very quickly.