At the 2016 Open Source Conference in Rome, held a few weeks ago, MariaDB was present along with many of the most relevant players in the Open Source community. This included the Italian Public Administration. They are required by law to give preference to free software and open source software. The goal of the Italian Open Source Observatory is to promote the use of open source software in Italian public administrations. They monitor and collect information on cases of open source adoption and best practices related to open technology usage within institutions.
One of the key issues in 2016 for DBAs to tackle will be Database Security, mainly associated to the increasing adoption of public and private clouds, as well as mission critical applications running on open source databases in large Enterprises.
In December 2015, MariaDB Evangelist Colin Charles was asked to present on MariaDB Security and Encryption at the London MySQL Meetup group. This blog is a summary of Colin’s presentation.
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.
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.
My relationship with Colt Engine, the Italian Joomla! Provider started in March 2011, when SkySQL was still a very “young” company and they got in touch with me to have more details on our new company. Since then many things happened on both the SkySQL (and then MariaDB) and the Colt Engine side. During the last two years they become a strong contributor to the MaxScale project (this will be better explained in a blog post later).
MariaDB MaxScale is now RC and together with all the MariaDB team that has been involved in the project we need to thank all the companies that agreed to become part of the MaxScale Beta Test Plan. This major step in the MaxScale life (read more here) had an important impact on the MaxScale QA process.
We have asked some companies to help us in testing MaxScale in “real” environments with different custom settings, different configurations and with traffic load as close to reality as possible.
I am back from 2014 Amsterdam Drupalcon where MariaDB Corporation was present as sponsor. It was my first time there and I must say I was really impressed by the amount of people attending the conference (around 2300 people) and the interest that the people showed for MariaDB.
MariaDB replication in general works as follows: on a master server, all updates to the database are written into the binary log as binlog events, a slave server connects to the master and reads the binlog events and applies the events locally to replicate the same changes as done on the master. A server can be both a master and a slave at the same time, it is thus possible for binlog events to replicated through multiple levels of servers.
The best way to get started with MariaDB TX or MariaDB AX is to download it right now!