Postgres Is Enough
20 points by blainsmith
20 points by blainsmith
An entirely AI-generated site telling me to use x tool over y tool is useless. It doesn't speak to developer experience, because it can't experience. It's just slop and wasted bytes on what is effectively marketing copy so that you'll click through to the AI consultancy in the footer.
Maybe worth highlighting the differences with e.g. https://lobste.rs/s/kjb4gb/just_use_postgres ?
Having just left a company that did basically this, I have to disagree. Some of our biggest issues were related to JSONB GIN indexes and using it as a job queue causing lock contention.
Were there ways to get around them? Most likely yes. But sometimes it is actually easier to reach for a specialized tool.
So if you are planning to do this, design your system so when you need to move stuff out of Postgres you can minimize suffering.
Why would you use JSONB GIN indexes in job queue?
I have worked in a high-traffic fintech that lived and breathed postgresql. We had our own issues (mostly because we arrived at this idea a earlier than most and had to develop some of our own unique tooling), but at current time looking at technological landscape most of the issues we had with PG are resolved.
Why not just use SQLite3 for everything? (At least at our scale. Or uh... I encouraged Lobsters to migrate but there were problems, although I never understood what they were and think some configing would solve it.)