The MariaDB Evolution: Just a fork of MySQL?
summary
Claims MariaDB is not just a fork backed by concrete differences: pluggable storage engines like INNODB MyRocks and ColumnStore that let a single query touch different engines, an example of a 4 million row analytic that runs much faster on columnar storage, an MaxScale proxy that does read write splitting CDC and automatic failover, a Kubernetes operator in development and an upcoming MariaDB Vector feature. Adoption metrics include about 75 percent of Fortune 500 usage and over one billion Docker downloads and a working Raspberry Pi cluster demo.
AI-written summary · about
chapters (18)
- 0:00MariaDB evolution intro
- 0:43Beyond MySQL fork
- 2:06Relational DB history
- 8:31MySQL origins
- 10:44Why MariaDB forked
- 11:48MariaDB growth
- 13:15Storage engines
- 15:45Cross-engine queries
- 16:50ColumnStore analytics
- 18:57Enterprise and MaxScale
- 21:06MaxScale proxy
- 22:10Read-write splitting
- 23:57MariaDB deployments
- 25:43AI vector search
- 26:47Migration tools
- 28:09Notable users
- 30:44Conclusion
- 31:25Q&A
related talks
45mThe MariaDB Evolution: Just a fork of MySQL?
41mMariaDB The New MySQL
26mThe Evolution of MariaDB: From MySQL to SkySQL
17mState of MariaDB
47mOn the past, present and future of Open Source databases
53mMariaDB Server 10.2: The Complete Guide
30mWhat’s New in MariaDB Enterprise Server
27mState of MariaDB