Remember our open letter, Looking for MySQL 5.7 or 8.0 guinea pigs?
We caught a nice guinea pig, a German one, from Hannover. They are currently using MySQL 5.7 (as was our prime wish), and they will be doing a live migration to MariaDB 10.11. They have 1.000.000.000 queries a day, their database size is 412 GB, and our goal is to the migration of the production data in less than five minutes – during our MariaDB Migration Workshop at our pre-FOSDEM event on Friday 2 Feb 2024.
“Generative AI is a can of worms that has to be opened”. That was the laconic comment from a senior industry influencer, when I shared MariaDB Foundation’s plans for successively making MariaDB Server a platform for AI solutions. The statement combines the opportunity with the inevitability, the complexity with the need for stepwise refinement.
Are we late to the game? I believe not. I believe this is the right timing. Open Source isn’t a pioneer when it comes to basic research or even early product development.
MariaDB Server has lots of energy and potential to increase its impact amongst Open Source RDBMSes. As the CEO of MariaDB Foundation, I’m happy to note that I can finally share a positive outlook for the next chapters in the story of MariaDB Server, based on what is happening with its namesake commercial entity, MariaDB plc. After years of missed opportunities, let me share with you why and how I have entered into this positive mood.
Let me begin by reiterating what is clear only to those following MariaDB Server very closely, namely that MariaDB Foundation and MariaDB plc are two separate entities, with separate governance, separate staff, and separate – although not conflicting – goals.
When setting long-term goals, striking the right balance is difficult: Not too generic (fluffy), not too specific (micromanagement). Not too few (lack of challenges), not too many (overwhelming). Consistently focusing on core values, while adapting to changes in the environment.
MariaDB Foundation’s internal goal setting process for 2023 seems to be working out well – and some lessons learned may be of interest even to our community.
The most important lesson learned is about our half-year review.
We set our 2023 yearly goals in December, with an emphasis on the first half of the year.
In a movie theater near you, expect to soon see an explanation of MariaDB Server and MariaDB Foundation in your own language! That is, providing you speak one of the good dozen of languages we have frequently encountered in the MariaDB Server ecosystem.
Like a majority of the MariaDB Server users, most of the developers behind MariaDB Server are non-native English speakers. We use Bad English as our lingua franca. Our pronunciation may be bearable to OK, but as with most techies, our understanding of written and spoken English is OK to good.
It may be long overdue, but based on recent events, we have launched Code of Conduct project at MariaDB Foundation. Our aim is to get your feedback and define a CoC, ideally by end of January, if we see convergence.
In the meantime, if we see unacceptable behaviour on the MariaDB mailing list or elsewhere, we will take action. We want to extend our apology to those who have had unpleasant experiences, about which we have done nothing in the past.
As for the code of conduct wording, our goal is to keep it short. Lofty goals often trigger distractive debates;
Today, MariaDB Corporation announced that it completed its merger, landing on NYSE as “MRDB”. With MariaDB Corporation being our founding member as well as our primary code contributor, we want to congratulate what is now MariaDB plc for this remarkable achievement.
MariaDB Foundation and MariaDB Corporation, while independent entities, share a joint interest in the development and adoption of MariaDB Server. In the new scenario with what is now to be referred to as MariaDB plc being a publicly traded company, we expect further interest in MariaDB Server by the ecosystem and community.
In the previous blog we have seen how to create a statefulset MariaDB application. Also, we learned how replication works in MariaDB in this blog. Now, we will try to create a replicated statefulset application. As good references for creating this blog, I would like to give credit to the Kubernetes documentation as well as an example from Alibaba Cloud.
To replicate a MariaDB application we are going to create a statefulset that will consist of a single init container and one application container.