1. 4SO
  2. Products
  3. DBaaS Enterprise

Database lifecycle control plane

DBaaS Enterprise

Database operations, not just provisioning.

A lifecycle control plane for ten database engines with 1/2/3-node topologies, engine-native HA semantics, backup/restore, upgrade and runtime verification.

  • MySQL
  • PostgreSQL
  • Redis OSS
  • Valkey
  • MariaDB
  • MongoDB
  • ClickHouse
  • OpenSearch
  • ScyllaDB
  • Qdrant
The DBaaS Enterprise control plane and database engines on separate plinths.
Who it is for
Database and platform teams that offer databases to other teams as an internal service.
What it does
Provisions, scales from one to three nodes, backs up and restores, upgrades and fails over ten engines through one traceable path.
Where it runs
On your own servers. The Manager is control-plane only and never sits in the database data path; clients connect through one stable FQDN.
FAILOVER · FENCING · QUORUMHow the database service continues when the primary is lost
01

The application writes to the primary through a stable endpoint.

01Problem

Provisioning is the easy part; operating the database is the product.

Replication, quorum, backup, restore, upgrade and failover differ by engine. DBaaS preserves those differences while presenting one durable operational surface.

  1. 01

    Lifecycle after creation

    Scale, backup, restore, upgrade and recovery are first-class actions.

  2. 02

    No fake abstraction

    InnoDB, Patroni, Sentinel and Galera keep their native quorum/election behavior.

  3. 03

    Designed recovery

    Promotion, fencing and rejoin rules exist before an incident.

  4. 04

    Observed success

    Membership, endpoint and client I/O must confirm the result.

02Capabilities

One operational surface, engine-specific mechanics.

The operator sees a coherent lifecycle while each engine keeps the coordination model it actually requires.

  1. 01

    Create service

    Engine, version, topology and nodes with preflight.

  2. 02

    1 → 2 → 3

    Add members without treating two nodes as automatic HA.

  3. 03

    Data protection and recovery

    Engine-native backup, integrity evidence and post-restore verification.

  4. 04

    Controlled change

    Supported version edge, backup gate and runtime read-back.

  5. 05

    Promotion / routing

    Engine-aware promotion or Galera routing reconciliation.

  6. 06

    Stable client identity

    Tenant FQDN remains stable across topology changes.

  7. 07

    Real signals

    Host/database telemetry and service-level probes.

  8. 08

    TLS, RBAC and audit

    Access and every operation stay controlled and traceable in the control plane.

03Deployment model

Topology follows the engine, not a generic HA checkbox.

The relational and key-value profiles (MySQL, PostgreSQL, Redis, Valkey and MariaDB) start at one node, grow through two nodes without automatic failover, and reach automatic HA at three members using the engine's own coordination model.

ProfileEnginesFailure behaviorNative mechanism
1 nodeMySQL · PostgreSQL · Redis · Valkey · MariaDBNon-HASingle member + stable endpoint
2 nodesMySQL · PostgreSQL · Redis · Valkey · MariaDBAutomatic failover disabledPrimary/Mirror or two-member Galera without majority
3 nodesMySQL · PostgreSQL · Redis · Valkey · MariaDBAutomatic HAInnoDB Cluster · Patroni/etcd · Sentinel · Galera quorum
04Lifecycle

The lifecycle is one durable loop.

Every mutation is admitted, persisted, executed, read back and either verified or moved into an explicit recovery state.

  1. 01Createengine · version · topology
  2. 02Scaleprepare · join · sync
  3. 03Backupartifact · integrity
  4. 04Restorepreflight · restore · verify
  5. 05Upgradeedge · stage · read-back
  6. 06Failoverfence · promote / reconcile
  7. 07Rejoinmembership convergence
  8. 08Removesafe member removal
05Engines

Ten engines, each with its own native semantics, under one Control Plane.

The control plane is shared, but replication, election/quorum, local routing, backup and failover/recovery follow each engine's native architecture.

EngineNative topology / routing1 node2 nodes3 nodesData protection
MySQLInnoDB ReplicaSet (1–2) · InnoDB Cluster / Group Replication (3) · MySQL Router on DB nodesNon-HAManual promotionAutomatic HAXtraBackup
PostgreSQLPatroni + Streaming Replication · etcd + PgBouncer + HAProxy on DB nodesNon-HAManual promotionPatroni automatic HApg_basebackup
Redis OSSReplication + Sentinel + HAProxy; Sentinel and proxy stay on DB nodesNon-HAManual promotionSentinel automatic HARDB / AOF
ValkeyReplication + Sentinel + HAProxy; a separate engine, not a Redis aliasNon-HAManual promotionSentinel automatic HARDB / AOF
MariaDBGalera (wsrep) + HAProxy; multi-primary cluster with product-routed write targetSingle-member GaleraNo automatic failoverGalera quorum HAMariaBackup / Logical Dump
MongoDBDocumentTopology, HA and data protection follow the engine's own native semantics, under the same control plane and lifecycle.
ClickHouseColumnar analytics (OLAP)Topology, HA and data protection follow the engine's own native semantics, under the same control plane and lifecycle.
OpenSearchSearch & log analyticsTopology, HA and data protection follow the engine's own native semantics, under the same control plane and lifecycle.
ScyllaDBWide-columnTopology, HA and data protection follow the engine's own native semantics, under the same control plane and lifecycle.
QdrantVectorTopology, HA and data protection follow the engine's own native semantics, under the same control plane and lifecycle.
Technical reference

Architecture, workflows and operations in detail

For engineers who want to know how the product works underneath: components, boundaries, failure behavior and the operations it runs.

06Architecture

Control Plane stays out of the tenant data path.

Intent and durable job state live in the manager; database runtime, membership and local routing stay on tenant database nodes.

  1. ENTRY
    Panel / Product APITenant, project, engine, topology, permission and confirmation.
  2. DURABLE STATE
    PostgreSQL operationsOperation, lock, correlation and audit persist before mutation.
  3. EXECUTION
    Outbox → RabbitMQ/Celery → AnsibleSerialized engine-specific execution on tenant DB nodes.
  4. RUNTIME
    Database nodes + local router/proxyThe serving system owns replication and routing truth.
BoundaryMechanismOperational contract
ManagerControl plane onlyNever a DB member, witness, quorum voter or failover target.
Stable endpointTenant FQDNClient identity survives topology changes.
RoutingLocal Router/HAProxy on DB nodesA client reaching any service node can still reach the correct role.
CoordinationEngine-native quorum/electionNo external witness is added to invent HA.
TECH

Execution pipeline. In DBaaS, accepting a request is not the same as completing the operation; a mutation is not finished until runtime read-back and evidence are complete.

StageAuthority / ComponentTechnical contract
AdmissionPanel / Product APIEngine, topology, permission and confirmation are checked; the request is only admitted.
Durable statePostgreSQLOperation and Job persist before mutation; only one active mutation is allowed per tenant; a second request is refused, not queued.
DispatchTransactional Outbox → RabbitMQ → Celery WorkerWork publication is coupled to transactional state and the worker receives serialized execution.
Execution fenceExecution lease + signed source manifestThe runtime tree must match expected release identity; drift blocks playbook execution.
Engine executionProject-local AnsibleThe native engine playbook runs only on tenant DB nodes; the Manager never enters the Data Plane.
VerificationEngine runtime + stable endpointMembership/quorum, replication, DNS/TLS and client read/write are read back from the real runtime.
EvidenceJob-scoped evidenceResult and correlation stay attached to the same Operation; HTTP acceptance never becomes completion by itself.
07Workflows and failure

Accepted is not succeeded.

One active mutation per tenant prevents overlapping topology changes; runtime evidence closes the job.

  1. 01AdmissionENGINE · TOPOLOGY · RBAC
  2. 02PersistDURABLE OPERATION
  3. 03QueueQUEUED
  4. 04ExecuteRUNNING
  5. 05Read-backVERIFYING
  6. 06TerminalSUCCEEDED / FAILED
FAILOVER PATH

Failover with fencing and quorum

The stable endpoint moves only after the new serving role is proven.

STABLE ENDPOINT
↓
PRIMARY
⇄
REPLICA
↓
QUORUM
+ FENCE
Failure → membership read-back → fence → promotion → route update → client verify
RECOVERY FORK

Restore: promote or abort

A recovery point must verify before it can enter the serving path.

BACKUP + CHECKSUM
↓
RESTORE
VALID?
↓
PROMOTE
RESTORED
↙ ↘
ABORT
ISOLATE
Compatibility · ownership · disk · engine health · client read/write
RECONCILIATION LOOP

Rejoin / replace loop

Observed membership decides whether a node can rejoin or must be replaced.

DESIRED
MEMBERS
→
RECONCILE
↓
READ
BACK
↑
OBSERVED
MEMBERS
←
DRIFT /
FAILED NODE
Rejoin eligibility → re-seed if needed → membership sync → endpoint verify
  1. Flow 01

    Provision Service

    From intent to service-level read-back.

    1. Engine / Version
    2. Topology / Nodes
    3. Preflight
    4. Persist Job
    5. Engine Automation
    6. Runtime Verify

    Failure and recoveryMissing membership, endpoint or client I/O evidence keeps the job non-successful.

  2. Flow 02

    Scale 1→2→3

    Grow without inventing two-node HA.

    1. Capacity Gate
    2. Prepare Node
    3. Join / Replicate
    4. Sync
    5. Quorum Check
    6. Endpoint Verify

    Failure and recoveryPartial membership is reconciled before another mutation.

  3. Flow 03

    Backup → Restore

    Protection is only useful when recovery verifies.

    1. Backup Admit
    2. Native Backup
    3. Integrity
    4. Restore Preflight
    5. Restore
    6. Client I/O

    Failure and recoveryIncomplete or corrupt backup is never accepted as a recovery point.

  4. Flow 04

    Upgrade

    Version change is staged and read back.

    1. Upgrade Edge
    2. Backup Gate
    3. Health Gate
    4. Stage
    5. Version Read-back
    6. Post-check

    Failure and recoveryUnsupported edge or degraded health blocks continuation.

  5. Flow 05

    Failover / Recovery

    Fencing and quorum precede promotion.

    1. Detect
    2. Read Membership
    3. Fence / Quorum
    4. Promote / Reconcile
    5. Route Update
    6. Client Verify

    Failure and recoveryMinority partitions are not force-promoted.

Additional operational flows

Two Day-2 paths that matter as much as initial provisioning.

  1. Flow 06

    Rejoin Member

    Return a recovered member without corrupting current membership.

    1. Detect Drift
    2. Fence / Classify
    3. Rejoin Eligibility
    4. Re-seed if Needed
    5. Join Membership
    6. Catch-up
    7. Endpoint Verify

    Failure and recoveryIf identity or replication position is unsafe, the node moves to replace instead of force-join.

  2. Flow 07

    Remove / Replace Node

    Remove or replace hardware while protecting quorum and retained members.

    1. Change Intent
    2. Quorum Gate
    3. Drain / Fence
    4. Remove Member
    5. Prepare Replacement
    6. Join / Sync
    7. Runtime Verify

    Failure and recoveryRetained members are not sanitized and the old node identity is released only after confirmed removal.

ActionAdmission / PreconditionsExecution ownerSuccess criterionFailure / recovery
Create ServiceValid tenant/project, engine/version, nodesDBaaS worker + engine playbookMembership + endpoint + client I/OFailed job retains evidence; reconcile before retry
ScaleHealthy current cluster + exact new nodeSerialized tenant mutationExact member count and replication/quorumPartial join is reconciled
BackupCompatible engine and destinationEngine-native backupArtifact + integrity metadataIncomplete backup is invalid
RestoreVerified backup + compatibility + maintenance gateCluster-locked restoreService + replication + endpoint + I/OUnknown outcome requires read-back
UpgradeSupported edge + backup + healthStaged engine-aware upgradeExact version + health + client I/OUnsupported/downgrade edge rejected; stops and recovers at the failed stage
FailoverEligible topology + fencing/quorumPromotion or Galera routing reconcileNew serving role + stable endpointRejoin/reconcile remains separate
08Operations catalog

DB operations become explicit product actions.

Operators work with lifecycle intent rather than memorized shell sequences.

  • Create database serviceEngine-aware deployment with preflight and runtime verification.
  • Add memberPrepare, join, sync and verify topology.
  • Create recovery artifactScheduled backup with retention and verify; native backup with integrity evidence.
  • Recover serviceCompatibility and service-level verification.
  • Change engine versionSupported edge and staged runtime read-back.
  • Move serving rolePlanned switchover and failover with quorum/fencing-aware promotion or reconciliation.
  • Repair membershipReturn a recovered node to valid membership.
  • Inspect serviceTopology, replication, endpoint and telemetry state.
  • Users & databasesCreate, grant, rotate passwords and drop through the same job path.
  • Certificate lifecycleCertificate status, renewal, reissue and product CA rotation.
  • Apply tuning profileResource-aware configuration profiles applied with ordered, safe restarts.
MCP

Remote MCP without a parallel authority. OAuth 2.1 Authorization Code + PKCE: the Panel is the Authorization Server and the MCP Addon the Resource Server; grants bind to the existing mcp_clients, RBAC, scope and rate limits instead of a second access model.

Database lifecycle as a product, not a runbook.

The control plane stays consistent while each engine retains its real topology and failure semantics.