[riku_iki]

what about failover story if server dies? PG failover setup is complicated, and cloud infra handles this for you.

[logifail]

(Genuine question) What's your current plan for when your cloud provider goes offline? Do you have a failover story, or it a case of "wait for them to come back online"?

[riku_iki]

I have backups on different cloud provider, so I could bootstrap db if provider goes dark indefinitely.

But realistically, I believe major clouds (google, aws) likely has more robust org and infra for recovery than I can built and maintain.

[positron26]

Do we mean managed or PG on K8s like CNPG? In all cases, I use the infra to simplify things like having disk redundancy and failover nodes, not because 12GB is interesting.

[riku_iki]

Primary managed PG, since you still need setup/maintenance/monitoring on your K8S own solution.

[positron26]

You guys are doing monitoring? ;-)

[tjwebbnorfolk]

What are you willing to pay for cloud-native failover?

Not every use case requires 100% uptime

[riku_iki]

Sure, but those who require (99% of major businesses) are ready to pay.

[Nextgrid]

Is that why most of them go down every time a single provider or even region goes down?

Actual active-active HA of your datastores is really hard to do (CAP theorem and all that). The majority of companies don't do it.

[riku_iki]

PG doesn't have active-active. Solution is to have multizone failover with replication.

[benjiro]

https://github.com/multigres/multigres ... when its complete. From the guy that made Vitess for Mysql.

And yes, i agree, the PG failover setup (and especially dealing with a failure afterwards, to restore the ex-master is beyond infuriating).

But its not pay 10x the amount, while eating easily 10x performance infuriating :)