Why PostgreSQL High Availability Matters and How to Achieve It

Re:Why PostgreSQL High Availability Matters and How to Achie... by tmpz22 on Wednesday June 14, 2023 @03:09PM (#36330997)

Different teams have different abilities. You can't really make general rules around any of this. Should you use spanner as a default selection for your company's database needs? Maybe.

[ Parent | on HN ]

Re:Why PostgreSQL High Availability Matters and How to Achie... by audioheavy on Wednesday June 14, 2023 @03:31PM (#36331327)

both good points, including the devs having different abilities and using a ready-made scalable solution. We're living in the world of having something working that you can test in a few days shrug

[ Parent | on HN ]

Re:Why PostgreSQL High Availability Matters and How to Achie... by hot_gril on Wednesday June 14, 2023 @07:14PM (#36334192)

Some general rules make sense for common use cases. Like, I'll say that a relational DBMS is generally what you want rather than a graph one. For a single-node DB, I'll always use Postgres if I have the choice.

But sharding is too use-case specific to prescribe something broadly like Spanner.

[ Parent | on HN ]