Conservative in-order parallel replication is a great feature in MariaDB 10.0 that improves replication performance by using knowledge of group commit on the master to commit transactions in parallel on a slave. If slave_parallel_threads is greater than 0, then the SQL thread will instruct multiple worker threads to concurrently apply transactions that were committed in the same group commit on the master.
MariaDB and Foedus paths crossed less than a year ago when I met Paolo Messina at a two-day IBM event in Tuscany. IBM invited me, as the MariaDB Italian representative, to introduce MariaDB as an Open Source Solution for the POWER8 platform.
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.
It was a very long time since I wrote something in this blob, but I have been very busy this spring with MariaDB on Power. This has been a lot of work, but also a lot of fun. So, what is this MariaDB on Power thing all about, well I wrote an introduction to the Power platform late last year. Since then a lot of things has happened.
Setting up data security correctly can be vital for systems at government agencies, e-commerce sites, hospitals and clinics, or any company with sensitive employee data. In this blog, Geoff shows you how to set up row-level security in MariaDB for use cases demanding more detailed privilege handling than MariaDB and MySQL provide out of the box.
Last week, an SSL connection security vulnerability was reported for MySQL and MariaDB. The vulnerability states that since MariaDB and MySQL do not enforce SSL when SSL support is enabled, it is possible to launch Man In The Middle (MITM) attacks. MITM attacks can capture the secure connection and turn it into an unsecure connection, revealing data going back and forth to the server.