Your e-commerce business depends on the integrity of your database. Should that database fail, the results could be catastrophic. You could expect to experience lost revenues, disgruntled customers and negative press.
As such, securing a database that is highly available is paramount to success.
When it comes to your database, generally speaking, there are three kinds of failure you might eventually experience: failure across a single node, failure across multiple nodes, and complete data center failure.
Today, let’s talk about the first kind of failure—that which occurs across a single node—and how ClustrixDB, a NewSQL cloud database with horizontal scale-out functionality, was designed to ensure your systems remain online should it happen to you.
With ClustrixDB, backup copies of each slice of data are automatically taken from each node and stored on separate nodes. The copies of data are called replicas, and they provide fault tolerance for the database.
Should a node fail, the database keeps running and no data is lost because every data slice has one or more replicas. Node failure will certainly result in you losing data slices, but no actual data is lost because the replicas already exist on different nodes. And following a single-node failure, the system will re-protect (rebuild new replicas) and rebalance (redistribute all your data across your available nodes) automatically.
In traditional MySQL databases, if you lose a slave node, it might not be that big of a deal. But if you lose the master node, you have a huge potential for complete failure. With ClustrixDB, all nodes are interchangeable, so you don’t have to shoulder the same worry.
As the owner of an e-commerce site, you have the most to gain—or, conversely, lose—from the availability of your database. Let’s say your database goes down for an hour. Can you really stomach that kind of financial hit?
The good news is that you don’t have to.