PostgreSQL is enough (2024)
gist.github.com
PostgreSQL is enough (2024)
1–10 of 97 posts
Re: PostgreSQL is enough (2024)
#2PostgreSQL is a powerhouse. It has a solution for everything. Especially when you start a project you might be better off just using PostgreSQL instead of a specialized solution. You can optimize it later.
Re: PostgreSQL is enough (2024)
#3[dead]
Re: PostgreSQL is enough (2024)
#4I like postgres. I use it for lots of projects. I like other databases too. I think thats okay.
Here's Malcom Gladwell discussing spagetti sauce which feels oddly relevant: https://youtu.be/iIiAAhUeR6Y?si=UJUUiF6H0j6IY3lL
Re: PostgreSQL is enough (2024)
#5> But the bar should be high: only after pushing Postgres to its limits, documenting why it was insufficient, and accepting the operational cost of the alternative
Why do I need to push Postgres to its limits before using a different solution? Throwing a hosted Redis in front of some hot-path API calls is very straightforward and easier to reason about than materialized views or UNLOGGED tables.
Re: PostgreSQL is enough (2024)
#6PostgreSQL is good enough until it's not good enough, when you realize all the bad design decisions that were made before it hits scale. It is the decisions people make around not partitioning, HA, replication that makes it not good enough.
Re: PostgreSQL is enough (2024)
#7Is it recomended for beginers?
Re: PostgreSQL is enough (2024)
#8PostgreSQL is good enough until it's not good enough, when you realize all the bad design decisions that were made before it hits scale. It is the decisions people make around not partitioning, HA, replication that makes it not good enough.
Re: bad design decisions - This can be said about any technology.
Re: PostgreSQL is enough (2024)
#9PostgreSQL is good enough until it's not good enough, when you realize all the bad design decisions that were made before it hits scale. It is the decisions people make around not partitioning, HA, replication that makes it not good enough.
Re: bad design decisions - This can be said about any technology.
+1 - when to prematurely optimise, when not to.
Re: PostgreSQL is enough (2024)
#10PostgreSQL is good enough until it's not good enough, when you realize all the bad design decisions that were made before it hits scale. It is the decisions people make around not partitioning, HA, replication that makes it not good enough.
That's fine. There are plenty of projects that don't hit that scale.