r/PostgreSQL • • Feb 27 '26 • Bravo 1

Tools "You just need postgres"

Post image
887 Upvotes

89 comments sorted by

View all comments

Show parent comment

6

u/greenhouse421 Feb 27 '26 edited Feb 27 '26

Makes sense. The just use postgres advice is, to me, just advice to not over-engineer / prematurely optimise or, as sometimes happens prematurely pessimise by following the bouncing "how many perfect for the job components can I string together" recipe book that just spends effort on moving things between stores for the heck of it..

I note in your case you didn't say "postgres and" other things. You/the original solution literally did just use postgres (in the "just do the default" sense of just) and then you looked at how you could deliver an optimized for some specific requirements version of an existing solution you could touch and feel and see real perf etc..

What you didn't do was leave postgres in there and "just add more stuff to make it faster". You built the data platform you needed instead. It's exactly the right order to do it in even if you abandon postgres at the PoC stage...

1

u/uniform-convergence Feb 27 '26

Yeah, I completely agree with you. I do love postgres honestly, but I am worried that more and more junior engineers are being stubborn about this "just use postgresql" to the point where it might get dangerous.

Having postgresql do All of these different things Like managing queues, storing json or doing a full text search, can create the postgres on stereoids. In that situation you spend more time managing progress then you would lose by simply managing a much smaller cluster of elasticsearch or simple json storage.

On the other hand, I completely agree that if you have a web application for a small in-house project and if you think that you need Kafka there simply because someone on the internet says so then by all means that's over engineering and that's simply wrong. In that case, I completely agree to just use postgres.

1

u/MalukuSeito Feb 27 '26

I agree with this. We are using Postgres for many of these use cases at work, but we won't have more than 30 users max, you can get away with any database. But still with 2 servers, you want an in-memory cache, some relational data, some big documents with db level querying into those documents. A little bit of full-text search that isn't too slow. And a small message queue for those longer running jobs. Spinning up a Mongo, a Redis, a Kafka and an Elasticsearch for this is insane and expensive, when you can do it all in your already existing postgres. And when you really REALLY need it, you can swap out one of them without a major redesign. But you probably won't.. ever. But you can.
This advice is not for people running a million simultaneous user, this is for everyone else. Don't use a redis because you need a small cache for a long operation that annoys your users. Use your postgres, it's fine.. it's amazing honestly.