MariaDB and the one-app-one-user habit

Practical notes on MariaDB in multi-service stacks: least privilege, connection hygiene, and why shared databases still need boundaries.

MariaDB (and MySQL-compatible tooling generally) powers a huge slice of self-hosted apps. The recurring failure mode is not the engine—it is shared credentials, unclear ownership, and migrations nobody wants to run twice.

A small discipline that ages well

• One database user per application with only the grants it needs.
• Document which stack owns which schema—wikis beat tribal memory.
• Backups tested on a schedule, not “when we remember.”

MariaDB’s own knowledge base at mariadb.com/kb is the canonical reference for server variables and migration notes.

Easy goin’, strict edges

Friendliness in ops comes from predictability. Predictability comes from boring database boundaries.