In the previous chapter, you learned what partitioning is, the types of partitioning, and querying on partitioned data, which helps in bettering performance.
We are going to discuss below topics in details:
Today, data is the most important part of any web, mobile, social, enterprise, and cloud application. Ensuring that data is always available is the top priority for any application. A small amount of downtime can result in significant loss of revenue and reputation for an organization.
Continuous availability of the data has become very critical in current time. And as the size of the data increases with time, it can become tricky to maintain huge amount of data available at any point of time. Losing a connection with the application for the fraction of a time can also make a huge impact on the organization and it can put the reputation of the organization at a stake.
To avoid any impact of inconsistency in application access because of the database, it is the demand of time to build up a highly available architecture. To build a highly available application infrastructure, many things are required to be considered, such as the capabilities of the technologies used for building...
MySQL replication works based on master-slave architecture. From group of MySQL servers, one server acts as a master and other servers work as slave server. All write operations are performed on the master server while read operations are performed on any of the slave servers. Connection between master and slave servers is done based on the configuration. In coming topics we will learn different configuration for synchronizing master and slave databases.
Let's quickly look at a few benefits of MySQL 8 replication.
As we said earlier, replication shares load between master and slave databases. So, now amount of activity for the database has been reduced. Master will only perform write operation and will not be worried about the read operations, while slaves will only be taking care of read operation without worrying about write operations. This mechanism actually makes the MySQL to perform faster. Also, it is easy...
A traditional MySQL replication implies to the master-slave architecture when write operations are performed by one server acting as master and other servers acting as slave are configured to periodically execute the replication to fetch data from the master and store locally. Each slaves in the master-slave replication has their own copy of the data and slaves do not share any information between them, basically we can term it as shared-nothing mechanism.
MySQL 8 has built in support for the Group replication. Group replication consists of more than one server each of which can act as master server. Servers in the group co-ordinate with message passing mechanism. For example, if any transaction commit operations is requested, it is relayed to the server group. Server group then approves a transaction and one of the server commits the write operation which then replicated to the group. For any read operation, no approval is needed from the server group and all such read...
In this chapter, you learned about high availability and why high availability is required. Then, we covered various replication methods to achieve high availability in MySQL 8 architectures and approaches. We understood different types of replication methods in MySQL 8 and the usability for each method. We also explored how to configure each type of replication with a few real-time examples.
Now it's time to move on to the next chapter, where we will see wonderful practices to achieve performance, scalability, security, and availability using MySQL 8.
© 2017 Packt Publishing Limited All Rights Reserved
