When you want to connect a client to a database server through an insecure network, there are two main choices: use SSL or use an SSH tunnel. Although SSL often may seem to be the best option, SSH tunnels are in fact easier to implement and can be very effective. Traffic through an SSH tunnel is encrypted with all of the security of the SSH protocol, which has a strong track record against attacks.
So I am now back in my office in Vancouver, BC after an amazing week in Santa Clara for the Percona Live MySQL Conference and Expo. I though that I would take a break from trying to catch up with my email and write down some quick thoughts about this great event.
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.
In the first blog of these series, we've done a rapid walkthrough on how to use Ansible and Vagrant to start a master/slave pair. In this second post, we will delve into the inner workings of Ansible, explaining how to set up server inventories, automate MariaDB deployments, use configuration templates and much more.
(The previous post, Better Parallel Replication for MySQL, is Part 1 of the series.) Parallel replication is a much expected feature of MySQL. It is already available in MariaDB 10.0 and in MySQL 5.7. In this post, a very nice side effect of the MariaDB implementation is presented: Slave Group Commit.
Upgrading a running MariaDB Galera Cluster from 5.5 (previous stable) to 10.0 (stable) is a question which comes up frequently with Remote DBA customers. Although a standard migration from 5.5 to 10.0 is well covered in the Knowledge Base, Galera Cluster upgrades haven’t been really documented in detail now. This howto will cover upgrades on CentOS or RHEL 6 but a similar logic can be applied to Ubuntu/Debian as well.
Last week we continued the MariaDB Roadshow in Europe and visited Paris, Brussels and Amsterdam. We have now completed 5 out of 10 events from this tour. The interest in this roadshow is overwhelming - in Amsterdam we even needed to put extra chairs into the room! So far attendees of the roadshow series especially liked topics around MariaDB MaxScale, security features in MariaDB as well as the MariaDB roadmap session. Monty was among the speakers in Helsinki and Amsterdam. But of course all the other speakers did a great job as well, including the people from Codership (Galera Cluster 4.0 new features) and IBM (Turbo LAMP stack with Linux on Power and POWER8).
Learning MySQL and MariaDB, Monty Widenius, one of the founders of MySQL and MariaDB, graciously contributed a Foreword. It's about six pages long and an interesting read for those who are familiar with MySQL and MariaDB. Of particular interest to newcomers to MariaDB, is the excerpt in this article on his perspective of MariaDB and his vision for its future, as well as MySQL.
MariaDB Galera Cluster is part of the easily deployed High Availability product MariaDB Enterprise Cluster. This blog raises a question about the behaviour of the bootstrapping method in MariaDB Galera Cluster.