Several other publicly available cloud offerings exist, providing high availability, elastic computing capabilities.

Tuxedo instances can be clustered to provide high availability for applications.

For high availability, the site uses two servers with complete full-text index replicas.

Nice work on that report about high availability and scale-out.

Well, high availability is actually not that easy to achieve.

One physical server is usually dedicated to each node for redundancy and high availability.

In this chapter, we discussed the unique high availability solution for MySQL using MySQL Cluster.

The principles for achieving high availability are simple enough.

Thus, you can use the heartbeat mechanism to perform automatic failover and similar high availability operations.

The same is true for guaranteeing high availability.

For more information about database high availability and MySQL high availability, see the following white papers:

In addition to handling an increased load, additional servers can support high availability and other business requirements.

Although they are not specifically tied to MySQL, these techniques are important tools for ensuring high availability.

In previous chapters, you learned about MySQL replication and its many uses for scale-out and high availability.

When configuring a MySQL cluster for high availability, you should consider employing all of the following best practices.

For high availability, data is automatically replicated, and failed nodes recover data by tapping replicas on active ones.