Discovering Azure's unannounced breaking change with Cosmos DB

Re:Discovering Azure's unannounced breaking change with Cosm... by nijave on Monday October 17, 2022 @09:23AM (#33233109)

We've talked to the Postgres product engineers many times. Proper solution is to run away from Single Server as quick as possible. Flexible or Citus Hyperscale may be good solutions. We're currently using Patroni to manage VM-based clusters (but still have a lot of data on SS)

Personally, I'd look into a 3rd party if you want managed Postgres (assuming you don't have contractual obligations that might complicate 3rd party access). There's vendors like EnterpriseDB, Scalegrid, etc that provide various solutions (I don't have any recomendations here--Postgres has a list of managed providers by country https://www.postgresql.org/support/professional_hosting/nort...)

[ Parent | on HN ]

Re:Discovering Azure's unannounced breaking change with Cosm... by llama052 on Tuesday October 18, 2022 @02:20PM (#33251706)

The hard part for us is figuring out how to migrate away from single server when it's used in production. It takes eternity to migrate data away from the thing, we are looking at ~24 hours just to get data out, and then we need to figure out how to do a live cutover or backfill.

Absolutely agree on a third party. Azure is just a let down overall.

[ Parent | on HN ]