The Layershift Logbook

Digital sovereignty is now part of how digital infrastructure is designed and operated across Europe and the UK.

Your architecture diagram has three application servers sitting behind a load balancer. It looks resilient. Everyone agrees it looks resilient.

Then one database node stops responding, and you find out what that diagram was actually worth.

Most MariaDB slowdowns don't arrive with a bang. There's no outage, no error, no obvious moment where things broke. The database just gets a little heavier to be around. A report that used to be instant makes you wait.

A query that used to be quick just showed up in your slow query log. Nobody rewrote it. Nobody touched the schema. Yet there it is, slower than it was last month. That single log line is often the first hard evidence that your database is drifting out of alignment with how it's being used.

A query that used to run in 50 milliseconds now takes 300. You didn't rewrite it. The schema looks the same. But it's slower, reliably, and it's getting worse. This is one of the most common signs that a database has drifted out of alignment with how it's being used.

If you only ever tune one thing in MariaDB, make it the InnoDB buffer pool. It's the pool of memory InnoDB uses to cache table and index data, and it's the difference between a query reading from RAM in microseconds and reading from disk in milliseconds.