MariaDB Server and MariaDB MaxScale provides a secure, high-performance database platform. Some aspects of security goes into MariaDB Server and some into MariaDB MaxScale. This blog post describes one of the security features of MariaDB MaxScale, the Database Firewall filter.
MariaDB Galera Cluster is a great way to implement High Availability with MariaDB and combining it with MariaDB MaxScale creates a great High Availability Cluster with transparent failover. Getting started with any HA solution is mostly a bit confusing as there are so many components that work together and each has to be configured to work with the other.
Data breaches are expensive. Between business disruption, loss of customer confidence, legal costs, regulatory fines and any direct losses that may result from a ransomware attack, for instance, the effects can add up to millions. The best defense is a good offense. In this blog, we'll look at five key practices to keep your database secure: protect, audit, manage, update and encrypt.
In this blog, we show you how you can use MariaDB MaxScale’s masking filter for sensitive user data masking.
When it comes to database high availability, how many 9s do you really need? Finding the right mix of reliability and infrastructure complexity is vital to make the best use of your resources. In this blog, we will take a high-level look at three common approaches, spanning from 99.9% to 99.999% uptime.
Now in the Microsoft Azure Marketplace: MariaDB TX 2.0 with MariaDB Server 10.2, configured in a MariaDB Galera Cluster topology, with MariaDB MaxScale 2.1, and Azure Managed Disks.
In this second installment of schema sharing with MariaDB MaxScale to combine SchemaRouter and ReadWriteSplit MaxScale routers, we'll go through the details of implementing it in order to shard databases among many pairs of master/slave servers.
Most of the time when you start a database design you don’t imagine how your applications need to scale. Sometimes, you need to shard your databases among some different hosts and then, on each shard you want to split reads and writes between master and slaves.
The 2.1.3 GA release of MariaDB MaxScale, introduces the following key features for the secure setup of MariaDB MaxScale Binlog Server:
The binlog cache files in the MaxScale host can now be encrypted.
MaxScale binlog server also uses SSL in communication with the master and the slave servers.
This blog covers how the binary log encryption works in MariaDB Server and in MariaDB MaxScale.
Performance is important and perhaps doubly so for a database proxy such as MariaDB MaxScale. When we started working with MariaDB MaxScale 2.1 we decided to make some significant changes to the internal architecture, with the aim of improving the overall performance. In this blog post, I will describe what we have done and show how the performance has improved.