Today, MariaDB Corp. announced that it has acquired a San Francisco-based database company, Clustrix. With this acquisition, MariaDB plans to add a scale-out capability that runs on-premises with commodity hardware or in any cloud environment. This, in turn, will provide greater scalability and higher availability than other traditional distributed options such as Oracle RAC.
MariaDB is an adaptable solution because of its architecture that supports pluggable and purpose-built storage engines.
Clustrix is a provider of relational database engineered for cloud and datacenter. Known for the scalability it provides, the ClustrixDB is an ideal database solution for high-transaction, high-value applications.
How will Clustrix acquisition benefit MariaDB?
Michael Howard, CEO, MariaDB Corporation, says, “With Clustrix, MariaDB can provide a better solution for our customers that have challenging scale-out enterprise environments. Our distributed solution will satisfy the most extreme requirements of our largest customers and gives them the freedom to break from Oracle’s lock-in.”
The company believes that the acquisition of Clustrix will allow MariaDB Labs to tackle the challenges in the database field. These challenges are extreme in distributed computing, machine learning, next-generation chips, and memory and storage environments.
Both Clustrix and MariaDB share the same vocabulary and work on similar problems. Also, both aim to be compatible with MySQL. This makes Clustrix a good fit for MariaDB.
Howard says, “the database was always built to accommodate external database storage engines. MariaDB will have to make some changes to its APIs to be ready for the clustering features of Clustrix. It’s not going to be a 1-2-3 effort, it’s going to be a heavy-duty effort for us to do this right. But everyone on the team wants to do it because it’s good for the company and our customers.” This simply means integrating the Clustrix database technology into MariaDB won’t be trivial.
To know more about this acquisition in detail, visit MariaDB blog