With the release of MariaDB MaxScale 2.5, if the primary node in a replication deployment fails, cooperative monitoring can automatically designate a new primary node.
MariaDB Platform X5 introduces scalable transaction processing: distributed SQL. Distributed non-relational (NoSQL) databases abound, but there are very few distributed SQL databases – and none like MariaDB Platform. Learn what sets it apart.
More often than not, replicas are deployed for high availability and/or read scaling. If the primary fails, one of the … Continued
This is the first in a series of short lightboard talks highlighting popular database topics. In this five-minute session, you’ll … Continued
We are happy to announce the general availability of MariaDB MaxScale 2.3.2. MariaDB MaxScale is the key application-facing component for … Continued
Introduction MariaDB MaxScale can do a few more things than you might think about at first. For example, you can have … Continued
This blog post is rather practical. What it aims to show is how we can use a script that in … Continued
Configuring database user accounts for MariaDB MaxScale and a backend cluster has typically required a duplicate effort. This is because … Continued
In this blog post, we look at how to configure Change Data Capture (CDC) from the MariaDB Server to MariaDB ColumnStore … Continued
Recommended Resource 2018 Webinar: First look at official Docker images and Kubernetes Helm charts for MariaDB Watch Now _________________________ There … Continued