MariaDB Dora Metrics: A Challenging RoadMap
4 min read
MariaDB is one of the most popular databases in the world. Created by the developers of MySQL, MariaDB has been downloaded more than 1 billion times. MariaDB is a powerhouse relational database management system (RDBMS), known for its speed, reliability, and user-friendly nature. And, with MariaDB in their corner, businesses can streamline their data processes, boost operational efficiency, and make smarter decisions backed by accurate, easily accessible data.
While this database management system boosts business efficiency, is it supercharging their own repository’s engineering workflow the same way?
Let’s see..
Subscribe to our newsletter for exclusive case studies and more!
Note: As part of our 100 days 100 case studies on open-source projects, we have been tracking the Dora Metrics of top open-source projects using, Middleware OSS.
Also read: Top 15 Software Development KPIs You Should Track in 2025
Our Analysis and Findings
MariaDB Engineering Workflow: A Challenging RoadMap
I shuddered seeing their engineering pipeline. All the metrics exceeded the benchmark Dora Metrics set by the State of DevOps Report 2023 which doesn’t look good for the repository.
For example, except for July 2024, their deployment frequency was under the standard of 50 deployments.
Their lead time took a significant hit, averaging 14.7 days, 13.5 days, and 10.4 days for July, August, and September, respectively, which was well beyond the established benchmark.
The main culprits for this prolonged duration from initial pull requests (PRs) to final delivery were weak first response times, high rework demands, and disappointing merge times.
Metrics | July | August | September |
First Response Time | 5.3 days | 10.9 days | 4.3 days |
Merge Time | 4.7 days | 1.6 days | 21 hours |
Rework Time | 4.7 days | 2.6 hours | 5.3 days |
Also read: Playwright - Plays it right with their perfect Dora Metrics
Key Reasons for the Inefficiency in MariaDB Engineering Workflow
Community Support Limitations: Although MariaDB has a dedicated community, it seems that it is not leveraging to its full potential. This can lead to longer response times for issue resolution or limited resources for advanced features.
Now, since they are spending around 40% of their time on pushing new features and around 30% on bug fixes, they should be encouraging more contributors to actively participate in the core process. Mentorship programs, training, and boot camps can help bring more hands-on board.
Now, since they are spending around 40% of their time on pushing new features and around 30% on bug fixes, they should be encouraging more contributors to actively participate in the core process. Mentorship programs, training, and boot camps can help bring more hands on board.
Documentation and Resources: The documentation for MariaDB, while improving, may not be as comprehensive or user-friendly as that of other database management systems like MySQL or PostgreSQL. Users may encounter difficulties in finding specific examples or troubleshooting guides. Note, that they are currently spending 20% of their time and effort on updating their documentation.
Fewer Built-in Tools: While MariaDB includes several powerful features, it might not have as many built-in tools for database management and monitoring as some of its competitors. Users may need to rely on third-party tools, which can complicate the setup and management process.
Also read: A Practical Productivity Guide for Engineering Managers of Distributed Software Engineering Teams
MariaDB: Lessons from Its Own Playbook
They really nailed it with the deployment of the PR that updated the Update markdown files for the main branch - Merged by LinuxJedi. This PR showcases some awesome qualities like small, manageable updates, teamwork in reviews, and quick merges.
They should capitalize on the way they handled this PR to enhance their workflow and ensure efficiency across the board.
MariaDB Dora Metrics: A Challenging RoadMap
MariaDB still has a bit of a journey ahead before it hits its peak potential. But if they take the time to understand what they’re capable of and really make the most of it, they can really smooth out their engineering pipeline. By honing in on their strengths, they can make things run much more efficiently!
If you find these learnings interesting, we’d really encourage you to give a shot at Dora metrics using Middleware Open Source. You could follow this guide to analyze your team or write to our team at productivity@middlewarehq.com with your questions and we’ll be happy to generate a suggestion study for your repo — free!
Also, If you’re excited to explore these insights further and connect with fellow engineering leaders, come join us in The Middle Out Community and subscribe to the newsletter for exclusive case studies and more!
Did you know?
MariaDB was created by Michael "Monty" Widenius, the original developer of MySQL after MySQL was acquired by Oracle. The name "MariaDB" comes from his daughter, Maria, continuing the tradition of naming after family members (MySQL was named after his other daughter, My).