PostgreSQL is one of the most capable relational databases available, but capability isn’t the same as suitability.
Using it to handle jobs it wasn’t built for – such as queuing or storing every document an application generates – creates recurring problems like unclear code ownership, single points of failure, security exposure, and rising cloud costs.
PostgreSQL expert Pat Wright explains more.
Stop putting everything in the database!
I’ve seen quite a few posts lately about how PostgreSQL can do everything. And, while I do believe it’s the most advanced and fastest-growing relational database available right now, that doesn’t