Say Hello to MariaDB TX

We believe an enterprise database solution requires technology, tools and services, and that it should be easy to buy, easy to deploy and easy to manage – providing a great customer and user experience from beginning to end.

In fact, we’ve made ease of use a central theme in our roadmap, and with the introduction of MariaDB TX today, we’re taking another first step – packaging MariaDB technology, tools and services into a unified offering to help customers succeed with MariaDB infrastructure: MariaDB Server, MariaDB MaxScale and MariaDB Cluster.

In addition to introducing MariaDB TX, we are releasing MariaDB Server 10.2 and MariaDB MaxScale 2.1.

MariaDB-Product Overview 17 May 2017 (1).png

MariaDB Server, MariaDB MaxScale and MariaDB Cluster (Galera Cluster for MariaDB), along with MariaDB connectors and drivers, form the base technology in MariaDB TX. By bringing them together, we are building a modular, integrated platform rather than separate, independent products – making them easier to deploy, easier to use and easier to manage … together.

In addition, MariaDB TX includes tools for administration (SQLyog for MariaDB), monitoring (Monyog for MariaDB) and backup/restore (MariaDB Backup) as well as notification services (e.g., security alerts).

And finally, to ensure customer success and satisfaction with MariaDB TX, we provide expert services for everything from database administration to enterprise architecture to migration management. In addition to technical support, customers can choose to extend their team with a remote DBA, a dedicated enterprise architect or migration project manager – resources with expert knowledge and experience.

A great way to learn more about MariaDB TX 2.0, including the new features in MariaDB Server 10.2 and MariaDB MaxScale 2.1, is to join our upcoming launch webinar.

If you want to dive right in, keep reading!

MariaDB TX 2.0

Product highlights

  • A comprehensive set of JSON functions in a relational database
  • An SSD optimized storage engine with unrivaled performance and efficiency
  • An advanced database firewall, complete with data masking

With MariaDB Server 10.2 and MaxScale 2.1, MariaDB TX 2.0 raises the completeness, compatibility, performance, scalability, security and disaster recovery of MariaDB – setting a new standard for open source database solutions in the enterprise.

Completeness and compatibility

First, we wanted to increase SQL completeness and schema compatibility. If you choose MariaDB TX over Oracle Database or Microsoft SQL Server, you should be able to perform similar queries on similar schemas. And while many of these features have long been available in proprietary databases, we’re excited to make them available in an open source database.



  • Common table expressions
  • Window functions
  • JSON and GeoJSON functions
  • EXECUTE IMMEDIATE statements
  • Subqueries within views
  • Multiple temp tables per query
  • CHECK constraints with expressions
  • DEFAULT values for BLOB/TEXT
  • DECIMAL columns up to 38 places
  • Multiple triggers per type per table

Performance and scalability

Next, we wanted to increase performance and scalability, focusing on storage, replication, querying and routing. At scale, improving storage efficiency and reducing disk IO not only improves performance, it reduces costs. Today, that means optimizing for SSDs, which is why we’re introducing MyRocks, a storage engine developed by Facebook for web-scale use cases.



  • MyRocks storage engine
  • InnoDB enhancements
  • InnoDB NUMA interleave
  • Virtual Column indexes
  • Fast connections
  • Optimizer enhancements
  • Query caching
  • Streaming inserts



  • Binary Log read throttling
  • Binary Log compression
  • Dynamic server configuration
  • Read-write splitting + master pinning
  • Multi-statement routing + master pinning

Security and disaster recovery

Finally, we wanted to increase security and disaster recovery. In particular, by expanding the capabilities of the database firewall by ensuring sensitive data was protected, prepared statements were examined and denial of service queries were prevented. For disaster recovery, we introduce point-in-time rollback a la Oracle Flashback.


Disaster recovery

  • Per user resource limits
  • Enforced TLS connections
  • Data masking
  • Prepared Statement filtering
  • Result Set limiting
  • Dynamic firewall rule configuration
  • Delayed replication
  • Binary Log based rollback