MariaDB PaaS using systemd multi-instance / socket activation
summary
Demonstrates running independent MariaDB instances on bare metal using systemd multi-instance and socket activation, merged into MariaDB 10.4 with ongoing work for 10.6. Uses Fedora 32, per-user data dirs and my.cnf templates, UID_MIN mapped to port numbers so uid 10003 becomes port 10003, and unix-socket authentication so each Linux user is DB superuser. Adds type=notify cooperation, SendSigKill=no safety, Restart=always, and cgroup limits. Demo launches four instances (Tom/Mary/Fran/one more) and socket activation starts services on first connection, and it works.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:59MariaDB on Shared Hosting?
- 5:20MariaDB's systemd story
- 8:22Current Systemd Implementation
- 17:32MariaDB Socket Activation (serverless)
- 18:06Systemd against Cloud Requirements
- 20:31Questions
related talks
28mMariaDB Database per user, on demand (aka systemd multi-instance socket activated)
34mOf Quadlets and Other Daemonless
51mMariaDB Scaling - From Single Instance to Multiple Clusters
38mRunning MySQL & MariaDB Server securely in 2019
17mState of MariaDB
21mSwitching from MySQL/Percona to MariaDB
50mMySQL/MariaDB Parallel Replication: inventory, use cases and limitations
53mMariaDB Server 10.2: The Complete Guide
