The beta version of the upcoming MaxScale 2.1 has been released. This new release takes MaxScale to the next level by introducing functionality that makes it possible to configure parts of MaxScale’s configuration at runtime.
The 2.1 version of MaxScale introduced a new concept of module commands. This blog post takes a look at what they are, why they were implemented and where you see them when you use MaxScale.
Performance has been a central goal of MariaDB MaxScale’s architecture from the start. Core elements in the drive for performance is the use of asynchronous I/O and Linux’ epoll. With a fixed set of worker threads, whose amount is selected to correspond to the number of available cores, each thread should either be working or be idle, but never be waiting for I/O. This should provide good performance that scales well with the number of available CPUs. However, benchmarking revealed that was not entirely the case.
We are happy to announce that MariaDB MaxScale 2.1.0 beta is released today. MariaDB MaxScale is the next generation database proxy for MariaDB. Beta is an important time in our release and we encourage you to download this release today!
MariaDB announced BSL 1.0 together with MariaDB MaxScale 2.0 in August 2016. After having the license “in the wild” for a few months we’ve been reaching out to Open Source advocates to get feedback on the BSL.
Join us for one of our full-day roadshows coming to a city near you! MariaDB is hosting educational roadshows across North America to showcase exciting new products and solutions, and share best practices for enabling critical enterprise features such as high availability and security. MariaDB experts will lead content-rich sessions on open source, product features, architecture and security.
From the very beginning, a central feature of MariaDB MaxScale has been its ability to understand the SQL statements that flow through it. For that purpose, MaxScale is equipped with an SQL parser for parsing statements.
Note: Replication Manager is developed and maintained by community members. It can be used with MariaDB Server, but it is not supported with an enterprise subscription (e.g. MariaDB TX).
This is a follow-up blog post that expands on the subject of highly available cluster, discussed in MariaDB MaxScale High Availability: Active-Standby Cluster.
High availability is one of the most important aspects of running a business. Whether it is a simple app for a small group of users or a large service used by millions, downtime costs a lot of money and ruins everyone’s day. No matter how hard we try, downtime is inevitable.
Today, I’m excited to announce the general availability of MariaDB MaxScale 2.0, our next generation database proxy. This new version includes important new functionality that integrates data streaming with Kafka and other data sources, as well as significant development work for better security and high availability.