Database model
Managed database connection service
Managed database connection service
Cloud MariaDB database
Database connection service for apps that use managed MariaDB offerings instead of running MariaDB in the stack.
This is the stack-side connection service for apps that should talk to a managed database server. It keeps the database wiring, secrets, and provider model inside Wodby while the actual database runs outside the cluster.
Overview
Technical profile and runtime packaging
Review how Cloud MariaDB is packaged as a Wodby database service, what it exposes at runtime, and which public artifacts it builds on.
Managed providers
Connect the stack to a managed database server
Cloud MariaDB sits inside the stack as the database connection service. It keeps app-side wiring stable while you point the actual database server at the managed provider that fits each environment.
Keep app connections consistent
Reuse the same database connection service across development, staging, and production while changing only the provider-specific database server behind it.
Offload database operations to the provider
Keep backups, scaling, patching, and infrastructure-level database operations with the managed provider instead of handling them inside the stack.
Keep the database close to the cluster
If you deploy the stack to AWS EKS, Azure Kubernetes Service (AKS), DigitalOcean Kubernetes (DOKS), and Google Cloud Platform Kubernetes Engine (GKE), keep the managed database on the same provider for faster network connectivity and tighter security boundaries.
Supported managed database providers
Stacks
Use it inside ready-made stacks or your own
These public stacks already use Cloud MariaDB in their database layer. Start from one of them, or build a custom stack around the same database service model.