MariaDB MaxScale 2.0 for data streaming requires configuring the MariaDB Master to send binary log events to MariaDB MaxScale, and configuring MariaDB MaxScale to receive and convert binary logs. This blog is a step by step guide to successfully receive binary log events from a Master database and convert them to AVRO records.
MariaDB MaxScale team has designed a modular solution to stream binlog events coming from the Master database to the data lake via messaging systems such as Kafka’s distributed broker. The binlog events for inserts, updates and deletes are converted in AVRO or JSON format before it’s forwarded to the data lake. Kafka is used as a data ingestion pipeline for distributed data process environment.
I am happy to see MariaDB Corporation announcing a major new version of MariaDB MaxScale. MaxScale 2.0 Beta is now available here.
Today, MariaDB MaxScale, the database proxy for MariaDB, is reaching its next major milestone – the availability of MariaDB MaxScale 2.0 Beta software release. Beta is an important time in our release and we encourage you to download this release today!
We are pleased to announce that MariaDB MaxScale 1.4.3 GA is now available for download!
URGENT UPDATE: Do not take 1.4.2 into use. We have found a problem and will provide a 1.4.3 release shortly.
We are pleased to announce that MariaDB MaxScale 1.4.2 GA is now available for download!
I was recently talking on the #mariadb channel on FreeNode and I got a question about the often overlooked PDF documentation generation. In this blog I will show how to create a set of PDF files of the MariaDB MaxScale's documentation - a good way to keep the documentation handy. I did this on Ubuntu 14.04, but it should also work on other platforms.
The MaxScale persistent connection feature has been available since version 1.3.0. It aims to reduce the load on the database servers in specific scenarios. Testing indicates benefits and feedback from live use has been positive.
MariaDB MaxScale, the dynamic routing platform for MariaDB Server (and MySQL Server) had its first stable 1.0 GA release 15 months ago. Since then, the popularity of MariaDB MaxScale has grown exponentially. It has in many cases become a default piece of the architecture in clustered setups of MariaDB Server, in master-slave replication setups and in very large replication topologies making use of MariaDB MaxScale’s Binlog Server functionality.
New and Improved Functionality
The recently released 1.4.1 version of MariaDB MaxScale contains a bundle of great improvements to the Database Firewall Filter, dbfwfilter. This article starts by describing the dbfwfilter module and how it is used. Next we’ll find out what kinds of improvements were made to the filter in MaxScale 1.4.1 and we’ll finish by looking at a few use cases for it.
Here are the highlights of the new dbfwfilter functionality in the 1.4.1 release of MaxScale.