Postgres is Enough . GitHub Gist: instantly share code, notes, and snippets.

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

This post discusses various use cases and libraries for working with PostgreSQL, including background jobs, message queues, GIS/mapping, audit logs, access control, search, foreign data integration, and HTTP.

Postgres is Enough

Just because you can, doesn’t mean that you should. There are real costs to having critical functionality buried inside postgres.
Not everyone knows how to use it. You can’t read it in the code. When stuff breaks, good luck finding why.

Move code into DB functions/triggers/procedures sounds like a good way to scratch your head N months later when something blows up or a requirement changes. I know I’ve been bitten by triggers that existed in a DB that the previous dev had set up but not documented, or at the very least, documented clearly.
Not saying there isn’t a place for functions in the DB - just don’t think the first link where it seems to be advocating for “Put all intelligence in the DB” is a great example.
SQL is great, no question - but it is also really finicky in my opinion - and at the end of the day, not every dev is going to be able to jump in and understand whats going on. Depending on your preferred setup - finding every function, stored procedure, trigger, and lord knows what else and then understanding the statements is … pretty intensive. Far easier, IMO, to find developers that can interface with a DB using &lt;insert language choice here and/or tools/libs&gt; than it is to find someone to do things in pure SQL/postgresql.

I haven’t used Postrgres for anything serious so far but I once visited hell after inheriting a project from a fired employee in my workplace who used lots of DB functions, triggers and procedures in Mysql, that’s not an experience I’d want to have again.

i don’t understant this fugging vibe with post , is oracle out of money ?

While PostgreSQL has a rich set of features for everything from GIS mapping to audit logs, painting it as the one-stop solution for all database needs is overly simplistic.
Take background jobs and message queues, for instance. Sure, PostgreSQL can handle these through extensions like PgBouncer or PgBoss, but is it always the best tool for the job? Modern applications often require more specialized solutions like RabbitMQ or Kafka for scalability and performance that PostgreSQL wasn’t specifically designed to handle tbh. Not sure what you are all using? Agree with several of the comments here though