Oracle MySQL is among the world’s most popular open-source databases and is widely used for websites like WordPress blogs. One of the unique and powerful features that has made MySQL extremely popular is its capability to support different storage engines. Depending on the storage engine used, MySQL can accelerate workloads including Online Transaction Processing (OLTP), in-memory OLTP, data warehouses, and Very Large Databases (VLDB). This solution uses the default InnoDB storage engine in MySQL 8.0 with the Dell EMC PowerStore T storage platform to accelerate and protect an OLTP workload.
The InnoDB storage engine leverages a combination of high performance and high reliability that makes it a strong choice for web applications. For example, many websites and web applications require the underlying database to support large volumes of reads and writes. Users might be logging into a website to comment on a blog, post a new blog, or search blogs on a range of topics. The modern InnoDB storage engine is designed to accelerate the volumes of reads and writes that comprise website traffic and similar workloads.
The InnoDB storage engine is ACID-compliant (Atomicity, Consistency, Isolation, and Durability), ensuring that all transactions are run in isolation. All transactions are committed or rolled back, maintaining data consistency throughout the database. The value to the enterprise is that the database can be recovered to a consistent point in time. For websites and mission-critical workloads, a fast recovery time limits risk, including the possible loss of revenue.
To address high availability (HA) and resiliency, MySQL provides the InnoDB Cluster. This is an Oracle HA configuration that uses group replication to commit transactions to all the MySQL databases in the cluster. The primary instance in the cluster supports reads and writes while the secondary instances are read-only. If the primary instance becomes unavailable, one of the secondary instances is promoted to primary. Therefore, using MySQL InnoDB Cluster enables the enterprise to survive the loss of a database server and still provide access to the database.