Historically MySQL is great in horizontal READ scale. The scaling, in that case, is offered by the different number of Replica nodes, no matter if using standard asynchronous replication or synchronous replication.

However, those solutions do not offer the same level of scaling for writes operation.

Why? Because the solutions still rely on writing in one single node that works as Primary. Also, in the case of multi-Primary, the writes will be distributed by transaction. In both cases, when using virtually-synchronous replication, the process will require certification from each node and local (by node) write; as such, the number of writes is NOT distributed across multiple nodes but duplicated.

The main reason behind this is that MySQL is a relational database system (RDBMS), and any data that is going to be written in it must respect the RDBMS …

I can’t express how grateful I am that you are here reading OpenLampTech each week. But, I’ll try anyway. Thank you! On to this week’s excellent content

Custom WooCommerce and Shopify Solutions

Discover useful WooCommerce and Shopify custom solutions for your online store today at affordable prices!

Learn More

The Newsletter for PHP and MySQL Developers

Receive a copy of my ebook, “10 MySQL Tips For Everyone”, absolutely free when you subscribe to the OpenLampTech newsletter.

OpenLampTech issue #78 has content featuring:

• MySQL backup tools you might not have heard of …

Discover how to troubleshoot a MySQL replica IO thread stuck in a connecting state. Learn about the replication architecture, security group rules for AWS EC2 instances, and how to address common issues like network restrictions and bind address configuration.

MySQL is a powerful database management and a widely used cloud database service. One of its key features is the ability to create replicas of a master database to improve its availability and scalability. However, at times the IO thread in a MySQL replica may get stuck in a connecting state, which can cause replication issues and affect the overall data consistency …

Amazon claims that Aurora has “Up to 5X the throughput of MySQL”. Is it true? It wasn’t easy to find the truth, but I kept digging until I found it. This is a long read; let’s chase the rabbit all the way down the hole.

Amazon claims that Aurora has “Up to 5X the throughput of MySQL”. Is it true? It wasn’t easy to find the truth, but I kept digging until I found it. This is a long read; let’s chase the rabbit all the way down the hole.

Amazon claims that Aurora has “Up to 5X the throughput of MySQL”. Is it true? It wasn’t easy to find the truth, but I kept digging until I found it. This is a long read; let’s chase the rabbit all the way down the hole.

Historically MySQL is great in horizontal READ scale. The scaling in that case is offered by the different number of Replica nodes, no matter if using standard asynchronous replication or synchronous replication. 

However those solutions do not offer the same level of scaling for writes operation. 

Why? Because the solutions still rely on writing in one single node that works as Primary. Also in case of multi-Primary the writes will be distributed by transaction. In both cases, when using virtually-synchronous replication, the process will require certification from each node and local (by node) write, as such the number of writes are NOT distributed across multiple nodes but duplicated. 

The main reason behind this is that MySQL is a relational database system (RDBMS), and any data that is going to be written in it, must respect the RDBMS rules ( …

Anomaly detection is a technique to find abnormalities in the data. It has found applications in a wide variety of fields such as fraud detection, network intrusion, detecting life-threatening medical conditions, quality control etc.

One of the best ways to learn is to read and study others’ fantastic content. And that’s just what I do each week in OpenLampTech. Get ready for another knowledge-packed newsletter. This is OpenLampTech.

Custom WooCommerce and Shopify Solutions

Discover useful WooCommerce and Shopify custom solutions for your online store today at affordable prices!

Learn More

The Newsletter for PHP and MySQL Developers

Receive a copy of my ebook, “10 MySQL Tips For Everyone”, absolutely free when you subscribe to the OpenLampTech newsletter.

In OpenLampTech issue #77, I’m looking at content covering:

• Linux File Permissions
• 5 Solid MySQL Books
• PHP isset() …

One of our customers recently had a Corrupted Index that affected the health of his database and caused latency for his customers. To identify and handle a corrupted index in MySQL, here are some common FAQs:

What is a MySQL corrupted index?

A MySQL corrupted index refers to a situation where the index data within a MySQL database becomes inconsistent or damaged, resulting in incorrect or incomplete query results. It can occur due to various reasons, such as hardware failures, software bugs, improper shutdowns, or disk errors.

What are the common symptoms of a MySQL corrupted index?

When a MySQL index is corrupted, you may experience several symptoms, such as slow query performance, incorrect or missing query results, frequent crashes or errors during database operations, or unusually high CPU or disk usage.

What are the common error messages related to MYSQL Index Corruption?

You can receive …