Create and filter basic records
Create a tasks table with id, title, status, created_at. Insert 5 rows, then return only rows where status='open' ordered by created_at DESC.
Data / Knowledge library
MariaDB
open-source relational database server
Why learn MariaDB?
MariaDB provides a reliable SQL database for transactional apps, analytics-friendly querying, and MySQL-oriented migration paths while staying open source and self-hostable.
Where it came from
2009: MariaDB was started by Michael "Monty" Widenius as a MySQL fork. It emerged after concern about MySQL stewardship following Oracle's Sun acquisition. MariaDB kept strong MySQL protocol and SQL compatibility to reduce migration friction. Over time it added MariaDB-specific capabilities and diverged in some features/behavior. The MariaDB Foundation supports community development, with commercial support also available.
- 2009: MariaDB was started by Michael "Monty" Widenius as a MySQL fork.
- It emerged after concern about MySQL stewardship following Oracle's Sun acquisition.
- MariaDB kept strong MySQL protocol and SQL compatibility to reduce migration friction.
- Over time it added MariaDB-specific capabilities and diverged in some features/behavior.
- The MariaDB Foundation supports community development, with commercial support also available.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Create a tasks table with id, title, status, created_at. Insert 5 rows, then return only rows where status='open' ordered by created_at DESC.
- Given an orders table, add an index on (customer_id, created_at). Run EXPLAIN for a customer history query before and after, and note what changed.
- Write a transfer script using START TRANSACTION, two UPDATE statements, and COMMIT/ROLLBACK handling. Include one failing case and verify balances stay consistent.
- Design a minimal primary-replica setup plan: binary logging, user privileges, backup seed, replication status checks, and failover caveats.
- Plan a zero-downtime column migration: add new column, backfill in batches, dual-write window, cutover query, and rollback steps.
More ways to practice
Index and inspect query plan
Given an orders table, add an index on (customer_id, created_at). Run EXPLAIN for a customer history query before and after, and note what changed.
Transaction-safe money transfer
Write a transfer script using START TRANSACTION, two UPDATE statements, and COMMIT/ROLLBACK handling. Include one failing case and verify balances stay consistent.
Replication readiness checklist
Design a minimal primary-replica setup plan: binary logging, user privileges, backup seed, replication status checks, and failover caveats.
Schema migration with rollback path
Plan a zero-downtime column migration: add new column, backfill in batches, dual-write window, cutover query, and rollback steps.
Documentation and sources
- MariaDB Docs Portal (mariadb.com)
- MariaDB Knowledge Base (mariadb.com)
- SQL Statements Reference (mariadb.com)
- Release Notes Index (mariadb.com)
- MariaDB vs MySQL Compatibility (mariadb.com)
Catalog research notes
- MariaDB 11.4 established an LTS branch for longer support windows.
- Recent 11.x releases continued optimizer and execution-plan improvements.
- Release tracks now better separate stability-focused adoption from faster feature delivery.
Connect the ideas
Explore next
Real World Example
Inventory Synchronization for Regional Retailers
A regional retail chain managing inventory across multiple physical storefronts and a centralized e-commerce platform.
The business problem
The retailer faces data inconsistency where local store inventory updates are not reflected in the central database in real-time, leading to overselling of items during high-traffic periods.
How this topic solves it
Implementing MariaDB Galera Cluster provides synchronous multi-master replication, ensuring that every node in the cluster contains the same data set at all times, allowing any node to handle read and write operations reliably.
- Configure individual MariaDB Server instances on separate network nodes.
- Install and enable the wsrep provider plugin to manage cluster state synchronization.
- Define the cluster address and node address in the configuration files to establish peer discovery.
- Initialize the cluster on the primary node and join subsequent nodes to the existing cluster.
- Verify cluster status using the wsrep_local_state_comment variable to ensure all nodes are in sync.
This diagram illustrates how regional store nodes synchronize with the central cluster.
Local inventory database
Local inventory database
Galera Cluster Coordinator
Read/Write interface
- Store_Node_1 → Synchronous Replication → Central_Cluster
- Store_Node_2 → Synchronous Replication → Central_Cluster
- E-commerce_API → Transaction Commit → Central_Cluster
Expected business outcome
The retailer achieves high availability and strong consistency across all locations, preventing inventory discrepancies and improving the customer checkout experience.
Limitations and checks
A significant tradeoff is the write latency overhead caused by the synchronous replication protocol, which requires all nodes to agree on a transaction before it is committed; this can be checked by monitoring the wsrep_flow_control_paused status variable.