Just Use Postgres By Denis Magda “just use postgres” is the modern architecture slogan. while simplifying your infrastructure sounds great, it doesn't always mean you've reduced complexity. often, you’ve just relocated it. That's when you're processing petabytes of logs across hundreds of nodes, or you need kibana's specific dashboards, or you have exotic requirements that genuinely exceed what postgres can do.
Book Review Just Use Postgres Vlad Mihalcea Stop defaulting to postgres for every single problem, do the hard architectural thinking, and pick the right tools for the right jobs. your future on call engineers will thank you. To me, the advice "you don’t need kafka, just use postgres" is doing more harm than good, leading to systems built in a less than ideal way, and i’d like to discuss why this is in more detail in this post. Just use postgres! covers recipes for using postgres in dozens of applications normally reserved for single purpose databases. written for busy application developers, each chapter explores a different use case illuminating the breadth and depth of postgres’s capabilities. "just use postgres" hit 532 points on hacker news in feb 2026. both sides of the debate have a point — and both miss something critical. here's the honest analysis.
Kafka Vs Postgres Just Use Postgres Just use postgres! covers recipes for using postgres in dozens of applications normally reserved for single purpose databases. written for busy application developers, each chapter explores a different use case illuminating the breadth and depth of postgres’s capabilities. "just use postgres" hit 532 points on hacker news in feb 2026. both sides of the debate have a point — and both miss something critical. here's the honest analysis. That's when you're processing petabytes of logs across hundreds of nodes, or you need kibana's specific dashboards, or you have exotic requirements that genuinely exceed what postgres can do. Over the last couple of years, we’ve been trying to reduce our need for other services in our apps, and that’s let us use postgres for more things. in most cases, we’ve been trying to cut redis out of the mix. redis is great, but adds one more dependency that needs to run and one more cost to bear. most apps don’t need it. The problem is that now you use postgres for 95% of your system, and also redis or nats, which means you lose the ability to atomically commit changes to your database and send a message in one transaction. Advice: when you are making a new application that requires persistent storage of data, like is the case for most web applications, your default choice should be postgres.
Comments are closed.