Postgresql-pilling everybody I can
for many uses, it's a %99+ chance your data set will never get big enough to justify choosing some other DB because it might "scale better"
aws Aurora's postgres version is even better than the og implementation too
Conversation
Replying to
I considered it... and then chose SQLite. Obviously there are tradeoffs... but it's so nice to have the N+1 problem basically go away.
1
5
It's extremely high performance when 1 concurrent writer with any number of readers. Far faster than a database server. I'll almost always use SQLite even if there are a fair number of writes if I know they won't need to scale up. That limitation is likely to fade away though.
2
1
These in-development features will change the situation quite a bit:
sqlite.org/cgi/src/doc/wa
sqlite.org/cgi/src/doc/be
BEGIN CONCURRENT provides fine-grained locking based on pages modified by transactions where contention is handled by application code with retries or locking.
PostgreSQL provides a huge amount of additional functionality but SQLite helps you out by making it much easier to do development / testing and not having a database server to manage. It'll be great when they land support for concurrent writes and I can stop using anything else.
1
