MariaDB

MariaDB is a MySQL-compatible SQL database. Many teams use it as a drop-in or migration path from MySQL, with its own performance and feature improvements.

Big picture: Databases overview

On this page

• When MariaDB is a good fit
• Create and deploy in dFlow
• What you’ll see on Overview
• Reference variables (MARIADB_…)
• Expose / Unexpose
• Everyday actions

When to choose MariaDB

Choose MariaDB when you want MySQL-style SQL and compatibility, or you’re standardizing on MariaDB for policy or performance reasons. If you need the MySQL brand/engine specifically, use the MySQL guide.

Set up MariaDB in dFlow

1. Applications → Environment → Add New → Add service → Database → MariaDB.
2. Create Service → open the service → Deploy.
3. Wait until Deploy completes; dFlow handles server setup for you.

Your connection details

After deploy, Internal credentials include a connection URL and separate username, password, host, port, and database name.

Note: Under the hood, the URL may look like mysql://…. That’s normal for MariaDB in dFlow. Use the fields on Overview; you don’t need to guess the format.

Use internal values for co-located apps. Public fields appear after Expose. Unexpose before Stop if exposed.

Link your app with reference variables

Open the Variables tab on your app or Docker service and use the `{ }` Reference variables picker. Example (rename my-mariadb to your service):

{{ my-mariadb.MARIADB_URI }}

Internet access (Expose)

MariaDB gets one public port when exposed, same idea as MySQL and Postgres. Prefer internal connections for app-to-database traffic inside dFlow.

Day-to-day management

Same pattern as other databases: Restart, Stop, Expose, Unexpose, and the rule that Deploy hides after the first success. Details: Where things live in the dashboard.

Useful links

• MariaDB
• MariaDB Server (source)