We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

MariaDB PaaS using systemd multi-instance / socket activation

Formal Metadata

Title
MariaDB PaaS using systemd multi-instance / socket activation
Subtitle
Bare metal, but still modern
Title of Series
Number of Parts
637
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Using baremetal and user level segregation, we can use systemd multi-instance to provide MariaDB as on demand PaaS, where every user gets their own configuration. This talk will show you what this looks like from a user and system maintainer perspective. With containers as all the rage, and the perceived default way of doing things, lets take a look at another approach of PaaS. Systemd as a service manager provides significant functionality on delivering multiple similar services in a managed way, so why not MariaDB PaaS? So with a few configuration changes from a default MariaDB install, let's show what a per user database instances looks like. Adding socket activation to mix and see "serverless" capability before it came fad with Kubernetes. On top of that, a brief look at abstract sockets that have been in MariaDB for while and what they could look like in a PaaS environment.