3 ms·
Yep I use orchestration (Nomad) but still you would need hardware redundancy. For example, the database server is currently a single point of failure. In the cl
by Axsuul 2y ago
Yep I use orchestration (Nomad) but still you would need hardware redundancy. For example, the database server is currently a single point of failure. In the cloud, if there's a hardware failure, it will simply go down and come back up with a new instance. In coloc, you'd need to have the data center debug and replace hardware which means extended downtime.
- NorwegianDude 2y agoWhen using colocation, nothing is stopping people from storing the database data externally from the server running the database like some cloud services do. But doing so, either in cloud or not, does have a serious downside: greatly increased latency.
- Axsuul 2y agoKind of defeats the purpose of colocation if you're not also running the database on your own server.
- sgarland 2y agoYou would not need to have extended downtime. Every major RDBMS that I’m aware of supports standby nodes, and if you want, a full active-active cluster (not recommended, personally). The downtime is as long as you have your health check monitoring interval set up for.
- nijave 2y agoPatroni will manage a PG cluster and auto fail over. I've heard of Stolon as well. If you're on k8s, there's a couple good operators that will handle this I believe paid PG vendors like EnterpriseDB and maybe Crunchy have their own tools