When people ask me about high availability, I often suggest that
it’s helpful to understand whether you’re most interested in
service availability, data availability, or both. Of course, you
want both — but if cost is an object, you may end up relaxing
your requirements.
The typical example of an application that needs service
availability but doesn’t have strong data availability
requirements is something that’s ad-supported. Who cares if the
last few comments on funny cat photos are lost? What’s important
is that the users can see the photos, and the ads next to them.
On the other hand, if you’re selling something, it’s a big deal
to lose records about orders or payments. In this case, if you
can’t have both kinds of availability, you might prefer downtime
over data loss.
Here’s a quick comparison of some MySQL high availability
technologies. All opinions are mine alone:
[Read more]