Constructing Hybrid Databases with MariaDB

Databases these days are comprised of so many elements that it’s important to remember to support a hybrid environment.

A modern database should no longer be transactional or analytical, relational or non-relational, on-premises or in the cloud.

It needs to support hybrid processing, hybrid data, and hybrid cloud. It needs to support hybrid everything.

DBTA recently held a webinar with Shane Johnson, senior director of product marketing, MariaDB Corporation, who explained how combining transactional storage and processing with analytical storage and processing in a single database allows enterprises to not only simplify database infrastructure, but enrich customer-facing applications with actionable insight.

“If a movie can be both a science fiction and a western…,” Johnson said. “A data model can be comprised of structured and semi-structured data.”

With JSON users get flexibility, simplicity, and ubiquity while relational databases give users data integrity, reliability, and the ability to do transactions.

Structured data is externally described and semi-structured data is self described, Johnson explained. Combining both gives users the best of both worlds.

Hybrid workloads are perfect for hybrid cloud and the MariaDB separates and isolates different workloads.

The platform can run different workloads on different infrastructure, place different workloads closer to different users, or scale different workloads on different hardware, Johnson said.

The MariaDB platform allows the database proxy to inspect queries and routes them to transactional and/or analytical database instances.

The change-data-capture stream replicates all writes from transactional databases to analytical databases within microbatches.

An archived on-demand replay of this webinar is available here.