| ▲ | eikenberry 2 hours ago |
| > The reason DBs like Mongo or Dynamo exist is because Postgres has a scaling problem. I've used Postgres at a few places and the #1 problem was always high availability, not scaling. One Postgres cluster could easily handle 100000 transactions per minute, but when a primary node went down it was a page and manually failing over to the spare then manually replacing the spare. The manual tooling was very finicky but at least it worked, no automated solution came even close. Lack of a good HA story is why I avoid self-managed Postgres as much as possible. |
|
| ▲ | levkk 2 hours ago | parent | next [-] |
| Good thing we support HA as well: https://docs.pgdog.dev/features/load-balancer/ Load balancer with health checks and failover, works out of the box. :) Battle-tested at this point too, so could be worth a look. |
| |
| ▲ | r7n 10 minutes ago | parent | next [-] | | I've extensively used Dynamo (internally at Amazon and externally) and even founded a DB startup with it at it's core. Boiling down scalability of Postgres vs Dynamo as it's written in blog is a bit terse. Dynamo scales writes horizontally with the keyspace, forever. Postgres simply can't, and no number of layers between the machines and the developer changes that. Sharding, pooling, Citus are all layered on top of an engine where a given row's writes still land on one
primary. | | |
| ▲ | zamalek 2 minutes ago | parent [-] | | Dynamo is a fundamentally different DB to Postgres. If your problem fits into the dynamo approach (I'd argue that more problems do), then you should be using it. No all problems fit, though. |
| |
| ▲ | eikenberry 2 hours ago | parent | prev | next [-] | | That's great news! I'll bookmark this in case I'm forced to manage Postgres again. | | | |
| ▲ | doctorpangloss 2 hours ago | parent | prev [-] | | Is a load balancer HA? | | |
| ▲ | dotancohen 14 minutes ago | parent | next [-] | | What happens when the load balancer fails? | |
| ▲ | gchamonlive an hour ago | parent | prev | next [-] | | Not by itself if it's naive, but if it's able to assess target health and avoid degraded instances then it becomes a component in HA, the other being integrating an orchestrator for gracious recovery. | | |
| ▲ | doctorpangloss 38 minutes ago | parent [-] | | from their docs: > PgDog does not detect primary failure and will not call pg_promote(). It is expected that the databases are managed externally by another tool, like Patroni or AWS RDS, which handle replica promotion. look, you guys can use a database tool from a guy who thinks he supports replication when the LLM he used to do everything correctly admitted that it doesn't support replication. i won't. | | |
| ▲ | nikolatt 6 minutes ago | parent [-] | | Why the snark comment? The PgDog project has been around for a while, it's not vibe coded. |
|
| |
| ▲ | dev-ns8 an hour ago | parent | prev [-] | | Combined with a replication strategy and automated health checks, a load balancer could direct traffic to a healthy instance automatically. |
|
|
|
| ▲ | parthdesai 43 minutes ago | parent | prev | next [-] |
| Patroni 1.0 was released in 2016, i.e ~10 years ago. https://github.com/patroni/patroni |
| |
| ▲ | nijave 4 minutes ago | parent [-] | | Yup Patroni handles automatic failures and cluster management quite well |
|
|
| ▲ | tempest_ an hour ago | parent | prev | next [-] |
| Patroni serves this niche pretty well at this point. |
|
| ▲ | globular-toast 2 hours ago | parent | prev [-] |
| Have you looked into things like CloudnativePG? https://cloudnative-pg.io/ |
