SSL (let’s call it that, even though SSL 2.0 and SSL 3.0 were long replaced by TLS 1.0–1.3 protocols) support was implemented in MySQL in 2001, so MariaDB (born in 2009) always had it. But over more than twenty years of SSL support there was one huge problem with it. It required tedious manual configuration, so most users never bothered and accepted the fact that their queries and data were sent unprotected. Which might have been slightly risky in 2001, but is definitely reckless in 2023.
Let’s see. First, the user installing MariaDB or MySQL has to generate a private key and a certificate.
The introduction of the StatefulSet resource was a game changer when it comes to run stateful workloads in Kubernetes, introducing a wide range of features, including:
- Predictable DNS names for each Pod, allowing one to individually address them in the network.
- Stable persistent storage for each Pod, ensuring that each of them is bound to the same PersistentVolumeClaim.
- Ordered graceful deployments and automated rolling updates.
However, this isn’t quite enough for running databases in Kubernetes in a reliable way. We are missing day 1 and day 2 operations, such as configuring high availability and scheduling backups, which is something not managed by vanilla Kubernetes.
There was a recent request by Eric Herman, the Chairperson of the MariaDB Foundation board, to add the time to first meaningful response for pull requests to the quarterly contributor metrics I generate and blog about. I thought this was a really good idea. There are a few problems with this, the first being the definition of “meaningful response”.
A “meaningful response” would likely be a response that adds value and shows that the pull request is being reviewed. The most accurate way to do this would be to manually record this using a set of criteria that defines what kind of responses are meaningful.
We are well into 2023 now, the time has really flown. There have already been two major versions of MariaDB Server that have reach GA, and with those, many new contributions. As with each quarterly metrics release, the raw data is available in our metrics repo, along with the scripts and configurations to generate it yourself.
We are tracking multiple MariaDB related projects at the moment, many of which are pulled in when you build MariaDB Server. These include:
- MariaDB Server – the server itself
- libmarias3 – an open source library to talk to Amazon S3 and related block storage services.
The MariaDB Foundation values our partnerships with our sponsors. Our partnership with IONOS allows us to get insight into how MariaDB Server is used and the direction it should take. As well as generally improving MariaDB Server in many different ways.
At CloudFest 2023, one of the first meetings we had was with Stefan Erkeling from IONOS. It was a very good meeting and it was great to see how much IONOS values our partnership. Stefan indicated in the meeting that there was a performance issue they were hitting and some advice was needed.
In a previous blog post, I gave an overview of the CloudFest Hackathon. At this event my team created a plugin for WordPress which added additional health checks for MariaDB. Since the Hackathon we have managed to get this plugin into the official WordPress plugin repository and are working on improving it.
The plugin is designed in a modular way with multiple parts that can be useful for WordPress administrators. The following is a breakdown of all the parts currently in the plugin.
One of the core features is gathering metrics about the queries executed.
Coding standards are often as hotly debated as vim vs emacs and other developer arguments. Viewers of the show Silicon Valley will all know the “tabs vs spaces” scene and how passionate people can be about it. Whilst I do personally have a preference (I’m not sharing it here), I feel it is much more important that people stick to one standard for a code base.
Several months ago a new community developer for MariaDB Server sent me a message asking where to find our coding standards document. After a bit of searching I realised we did not have one, and if we want to onboard new developers we definitely should have one.
Back in December, we asked for your feedback on implementing a code of conduct in the MariaDB Server community. We have seen some great feedback and observations from this and today we are have published version 1.0 of our code of conduct.
The feedback we have received has been generally positive both when it comes to implementing a code of conduct in general, and to the content of the text.
That said, it was suggested by Brian Andrus that we better define “inflammatory language”; this is something we actually discussed internally prior to the draft content.