Innodb Cluster or ClusterSet topologies already have secondary instances that can act as a failover for primary or also offload read requests. However, with MySQL 8.4, we now have the feasibility of adding a separate async replica to the cluster for serving various special/ad-hoc queries or some reporting purposes. This will also help offload read traffic away […]

MySQL Group Replication is a powerful feature that allows you to create a fault-tolerant and redundant database system, ensuring high availability and data consistency across multiple servers. The primary goal of this technology is to provide automatic failover and improve the overall system’s reliability. If one of the servers in the group fails, the others […]

Learn how to configure and manage MySQL Routing Guidelines using MySQL Shell's AdminAPI, with step-by-step examples for InnoDB Cluster, ClusterSet, and ReplicaSet - Enabling smarter and more dynamic query routing.

With the recent performance enhancements we have made in MySQL and HeatWave there is increased interest in customers using MySQL for more complex queries and more complex workloads and here we are taking another step by improving the semi-join performance. In older versions of MySQL 8.0 we saw the potential for optimizing simple semi-join queries using […]

Scalable systems live or die by schema clarity. That’s why most engineers now use database diagram tools to map, manage, and document their structures. But not all tools are built for modern, fast-moving teams. Here’s a look at the top database diagram tools making a difference in 2025.

The post Best Database Diagram Tools–Free and Paid  appeared first on Devart Blog.

In this blog, I am going to explain the complete process involved in the MySQL group replication setup using SSL. The blog covers the complete MySQL config files as well as steps. I used the following aspects for my testing purpose.

• MySQL 9.3.0 Inn ovation release
• Ubuntu 24.10
• 3 physical servers

I also enabled the hostname based authentications between the three VMs. So that, I don’t need to provide the IPs explicitly each time. To achieve this, I used to update the the file “/etc/hosts” with following entries.

root@gr1:~# cat /etc/hosts | grep gr
198.19.249.194 gr1 gr1
198.19.249.116 gr2 gr2
198.19.249.163 gr3 gr3

---- Test
root@gr1:~# telnet gr2 3306
Trying 198.19.249.116...
Connected to gr2.
---- Works!

Creating SSL certificates:

As I am going to setting up the SSL based group replication, I need to create the required certificates …

On April 22-23rd, 2025, the Oracle Conference Center in Redwood Shores, California, buzzed with excitement as the MySQL and HeatWave Summit 2025 kicked off. The MySQL and HeatWave Summit is the largest gathering of MySQL users, developers and product experts in the world. The summit brought together developers, DBAs, experts, and users for this two day event packed with learning, networking, and celebration of MySQL’s latest advancements.

On April 22-23rd, 2025, the Oracle Conference Center in Redwood Shores, California, buzzed with excitement as the MySQL and HeatWave Summit 2025 kicked off. The MySQL and HeatWave Summit is the largest gathering of MySQL users, developers and product experts in the world. The summit brought together developers, DBAs, experts, and users for this two day […]

Announcing Vitess 22 # The Vitess maintainers are happy to announce the release of version 22.0.0, along with version 2.15.0 of the Vitess Kubernetes Operator. This release is the first to benefit from a 6-month-long development cycle, after our recent change to the release cadence. Version 22.0.0 comes with significant enhancements to query serving and cluster management. These changes have allowed Vitess to be more performant and easier to operate compared to version 21.

While doing benchmarks on 5.7 and 8.0, I came across a performance regression in MySQL 8.0 over 5.7 and opened a bug (Bug #111353 : 3x Performance Regression from 5.7 to 8.0 on ALTER TABLE FORCE).  There has been recent activity on this bug, showing an easy workaround.  This, even if it is known since 16 July 2024, has not been talked about much, so this deserves a blog post.