MariaDB gets meaty on decoupled JSON data masked love

Open source database company MariaDB Corporation has moved to iteration MariaDB TX 2.0.

This now available version of the transactional database product has new server-specific MariaDB Server and ‘MaxScale’ capabilities.

Decoupled pleasure

MaxScale is a database proxy that extends the availability, scalability and security of MariaDB Server.

It, MaxScale, also aims to help simplify application development by decoupling it from the underlying database infrastructure.

Closing functional gap

Latest updates to this product also claim to be focused on closing the functional gap between open source and proprietary offerings.

“For too long, there has been a gap between the high-cost performance of proprietary databases, and the affordable, modern architectures of open source databases,” said Roger Bodamer, chief product officer at MariaDB Corporation. “MariaDB TX new features include support for MyRocks, JSON and data masking.”

Readers will note that data masking is a method of creating a structurally similar (but inauthentic) version of an organisation’s data for reasons such as software testing and user training.

JSON emerges, as a standard

In terms of the JSON support, MariaDB notes that JSON is really THE emerging standard for developers building web, mobile and IoT applications

As nicely defined here… JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data — it is used primarily to transmit data between a server and web application, as an alternative to XML.

However, says the firm, NoSQL databases built to support JSON are ‘too functionally limited’ (by MariaDB’s yardstick, at least) to support the majority of enterprise use cases. Meanwhile, relational databases have been slow to provide complete JSON support.

MariaDB TX 2.0 adds a  set of 24 JSON functions

Data masking

In line with this news, the firm says that data masking is a new feature which masks sensitive data before returning query results, protecting data that is classified as personal identifiable, personal sensitive or commercially sensitive data, common requirements for HIPAA/PCI compliance.

“Newly introduced result set limiting prevents Denial of Service attacks by specifying a maximum number or rows or data that can be returned in a query, prepared statement or stored procedure to prevent service interruptions,” said the company, in a press statement.

Also new is beta support for Facebook’s MyRocks, a transactional storage engine optimised for flash storage. Applications built on MariaDB TX 2.0 can utilize MyRocks for 2x compression, faster replication and data loading.

For additional colour on this story, Computer Weekly Open Source Insider received comment from Thomas Steinborn who oversees product management for cloud, platform and realtime at data integration company Talend.

“Data dasking indeed is a key enabler to data privacy regulations like the upcoming General Data Protection Regulation (GDPR). Smart data masking must preserve data relationships and referential integrity, e.g. by consistently masking primary and foreign keys,” said Steinborn. “The move of MariaDB to push data masking to the systems of records, will simplify valuable data at rest. Data integration tools will [further] complement the solution while your data is in transit.”

Fancy (but common) table expressions

Finally then, MariaDB TX 2.0 adds several new features that enhance query functionality, including common table expressions and window functions.

Common table expressions make complex database queries easier to read and easier to maintain by breaking queries down into simpler building blocks.

In all, is this enough new feature functionality to warrant a new release and version number? One has to say yes… there is meaty decoupled common complexity JSON data masked love here for sure.