Quantcast
Channel: Planet MySQL
Viewing all articles
Browse latest Browse all 18766

3-Steps to Deploying Mission Critical Web & Telecoms Services

$
0
0
There are multiple architectures that can be used to achieve highly available database services, each differentiated by the levels of uptime they offer.  These architectures can be grouped into three main categories:
- Data Replication
- Clustered & Virtualized Systems
- Shared-Nothing, Geographically-Replicated Clusters

As illustrated in the figure below, each of these architectures offers progressively higher levels of uptime, which must be balanced against potentially greater levels of cost and complexity each incurs. 

Simply deploying a high availability architecture is not a guarantee of actually delivering HA.  In fact, a poorly implemented and maintained shared-nothing cluster could easily deliver lower levels of availability than a simple data replication solution.

 
9s.png


To reduce risk and accelerate the evaluation process, we've recently developed some new resources that demonstrate how to get started with the MySQL Cluster database - a key option for users needing to deliver MySQL-backed solutions with 99.999% availability (i.e. less than 5 minutes downtime per year).

In this 3 x step series, we've shared best practices in installing / configuring / testing MySQL Cluster, then moving from evaluation into production deployment and practical guidance in optimizing application performance. 


•    Part 1: MySQL Cluster Deployment Best Practices
Listen to the On-Demand Webinar

•    Part 2: Getting Started with MySQL Cluster
Listen to the On-Demand webinar

•    Part 3: Guide to Optimizing the Performance of the MySQL Cluster Database
Download the Whitepaper

And of course you can feedback your experiences on the MySQL Cluster mailing lists and user forum

Happy clustering !


PlanetMySQL Voting: Vote UP / Vote DOWN

Viewing all articles
Browse latest Browse all 18766

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>