Database Platform
DBaaS Enterprise
A control plane for provisioning and lifecycle operations across MySQL, PostgreSQL, Redis/Valkey and MariaDB with explicit topology semantics.
- MySQL
- PostgreSQL
- Redis / Valkey
- MariaDB
- Backup / Restore / Failover
The problem
Problem
Database operations combine state, topology, quorum, routing, backup and upgrades; a simple UI must not falsify distributed-system truth.
Why It Is Hard
Different engines have different semantics and scale or failover is more than an inventory change; each mutation must preserve roles, quorum, endpoints and post-conditions.
The decision
Leadership / Architecture Role
Separated the manager from the data plane, defined explicit topology semantics and durable workflows for scale, failover, backup and upgrade.
Key Decisions
API and console share one authority, root-first management workflows are supported, and validators check behavior and contracts rather than substrings or variable names.
The architecture
Architecture
Control-plane state lives in PostgreSQL, operation state is durable, engine-specific orchestration stays in its owner layer, and stable endpoints live on the data plane; the manager is never a witness, router, proxy or failover target.
Failure & Recovery Model
Failover, backup and restore, scale and upgrades are modeled as resumable, verifiable operations; success is read from runtime state and endpoint behavior.
Security / Authority Model
Tenant, RBAC and audit stay in the control plane, while hardening is not allowed to break management SSH, recovery or the standard root workflow.
The value
Product Experience
Users choose engines and topology while orchestration details remain hidden only as far as failure semantics and limitations stay truthful.
Value Created
Specialist database operations become repeatable, auditable and recoverable workflows, reducing dependence on fragmented manual execution.
The boundaries
Trade-offs
A perfectly uniform abstraction across engines is intentionally avoided; the common lifecycle is preserved while engine-specific truth remains in the owner layer.
What Was Intentionally Excluded
Putting quorum roles, proxies or stable endpoints on the manager, or masking failures with optimistic status, is intentionally excluded.
Truth boundary
Current Truth / Limitations
Each engine and topology is represented only to the level supported by evidence; source/static PASS never substitutes for runtime certification.
designed → source implemented → runtime tested → production certified
Each level is claimed separately; a lower level never implies a higher one.
Start a conversation
If technology should move your organization forward rather than hold it back, let’s talk.
The first conversation is about your problem, not about me: where you are stuck, what is at stake and whether I am the right person to solve it.
Bring the problem