3 ms·
> What's wrong with hot standby, log shipping and heartbeat? It doesn't work outside the lab. I know that's audacious, but there's been plenty of Heroku based
by ssmoot 14y ago
> What's wrong with hot standby, log shipping and heartbeat?
It doesn't work outside the lab.
I know that's audacious, but there's been plenty of Heroku based services with outages because of just this. Automated failover to standby systems is very risky and IMO just never a good idea when it comes to your database servers. You also need a bullet-proof STONITH solution so you avoid the nightmare of split-brain on your database servers then. I mean who wants to have to manually consolidate customer data after a failure?
> I don't know how easy this would be with MVCC.
I didn't consider that. Good point. Still want it. ;-)
- mxd7 14y agoConsider taking a closer look at NuoDB. It has MVCC and an interesting distributed objects architecture for elastic scale out. http://www.nuodb.com/techblog/2013/03/13/mvcc-part-2-pretty-pictures-and-some-examples/ http://www.nuodb.com/techblog/2013/03/13/mvcc-part-2-pretty-... MVCC doesn't solve all concurrent access conflicts, only certain read-write ones, but snapshot isolation works well for many types of workloads.