In database setups with a large number of users reading data, the Binlog Server can be used to offload traffic to the Master, make Master failover easier to handle and in general simplify replication. In this blog I will describe the benefits of Binlog Server and how to set up MaxScale as a Binlog Server.
We are pleased to announce that MaxScale 1.3.0 beta is now open for the community. Read our blog regarding the latest new features, and where to find the release notes.
Having written the Building MaxScale from source on Centos7 tutorial, we have received requests about writing one for Ubuntu. It seems the most mentioned version is the 14.04 LTS version so we’re going to go with that. For the purpose of this tutorial, I’ve installed a fresh installation of Ubuntu 14.04.3 LTS (Trusty Tahr) on a VM.
MaxScale is a bit more complicated to build on Ubuntu and Debian, but should still be something almost everyone can do.
We’ve gotten a few questions on detailed installation tutorials for specific systems. So I decided to write one for CentOS 7 which is a pretty common OS. For this I’m using a fresh installation of CentOS 7 on a virtual machine.
In this blog we look at how MaxScale helps minimize database access down time for client applications. Following our partner Severalnines’ recent announcement we want to inform the MariaDB community know that there is an automation and management platform available to them, ClusterControl, that will help them deploy and manage MaxScale for MariaDB (which in turn also helps minimize downtime).
Parallel replication is a much-expected feature of MySQL. It is available in MariaDB 10.0 and in MySQL 5.7. In this 3rd post of the series, we present benchmark results from Booking.com production environments.
MaxScale 1.2.0 and above can call external scripts on monitor events. In the case of a classic Master-Slave setup, this can be used for automatic failover and promotion using MariaDB Replication Manager. The following use case is exposed using three MariaDB servers (one master, two slaves) and a MaxScale server.
In the last two releases of MariaDB Enterprise, we have provided enhanced performance with the introduction of certified MariaDB binaries for POWER8 and optimized binaries for the x86 platform. This Summer we make it more efficient and automated for developers and DBAs to use our high performance MariaDB binaries.
Recently, I asked Colt Engine to help us with the MaxScale Beta Testing process. They agreed to do this, but they had to find the best way to test a new environment, with MaxScale on top and with as little impact as possible on their datacenter. The traditional approach would be to create as many virtual machines as needed and configure them for the designed test environment. This is a valid approach, but it requires some time to setup and the unnecessary use of resources. Instead, they decided to use an “Application Container”; they decided to use Docker.
When we first announced MariaDB Enterprise last year in March of 2014, our goal was to deliver superior performance and customer experience in addition to a hardened and certified version of open source MariaDB Server. In the first release we delivered hardened and certified binaries, and with the second release in December 2014 we raised the bar in performance. At that time, we announced MariaDB Enterprise for the IBM POWER8 platform, with a 2.2x performance gain over the x86 platform.