RDS · DynamoDB · Redshift, one plane

Databases & Data

Relational, document, vector and analytics data — one governed database plane.

86operations
3services
15endpoints shown
4architecture seams

What it is

Relational, document, vector and analytics data — one governed database plane.

ADR-0056 makes the DBaaS the only database plane on the platform: every engine is a claim with placement, leases, CDC, point-in-time restore and key rotation. Prism turns product events into contract-checked metrics; Mediation rates and reconciles high-volume usage records. No shadow databases, no unmanaged data.

Auth is one model across every service here — an SS-01 bearer token plus X-Tenant-Id on every /api/v1 route. Public base https://api.nexocloud.io/api/v1.

Services & endpoints

3 real backends, 86 operations.

Every path below is a real route from services/<svc>/openapi.json. Each service lists a representative slice of its full contract.

DBaaS SS-02

58 operations

Managed database engines — claims across relational, document and vector engines with placement, CDC, leases, restore and rotation.

  • POST/api/v1/claimsProvision a database claim from the engine catalog.
  • GET/api/v1/claims/{name}/cdcRead the change-data-capture stream for a claim.
  • POST/api/v1/claims/{name}/queryRun a governed query against a claim.
  • POST/api/v1/claims/{name}/restorePoint-in-time restore a claim.
  • POST/api/v1/claims/{name}/rotateRotate a claim's credentials via Vault.
  • POST/api/v1/vector-claimsProvision a vector database claim for embeddings.

Prism Analytics SS-09

6 operations

Product analytics — contract-checked event ingestion, metric definitions and time-series query.

  • POST/api/v1/contractsRegister an event contract (schema) for validation.
  • POST/api/v1/eventsIngest a product event validated against its contract.
  • POST/api/v1/metricsDefine a metric over ingested events.
  • GET/api/v1/queryQuery a time-series metric window.

Mediation SS-36

22 operations

Usage mediation — CDR ingestion, deterministic rating against versioned rate decks, reconciliation and suspense repair.

  • POST/api/v1/cdrIngest a usage record (deduplicated, spooled when the sink is down).
  • POST/api/v1/rating/rateRate a record against the active rate deck with a deterministic breakdown.
  • POST/api/v1/rating/rerateRe-rate stored records in a window against the current deck.
  • GET/api/v1/reconcile/casesList open reconciliation cases.
  • POST/api/v1/suspense/{id}/repairRepair a quarantined suspense record.

Worked example

A database claim with CDC and point-in-time restore

Every database is a claim: provisioned from a catalog, streamed via CDC, and restorable to any instant — with credentials rotated through Vault, never held by your app.

  1. 1
    ProvisionPOST/api/v1/claims

    Pick an engine from the catalog; placement and leases are handled for you.

  2. 2
    Stream changesGET/api/v1/claims/{name}/cdc

    Consume a change-data-capture feed for downstream sync or analytics.

  3. 3
    RestorePOST/api/v1/claims/{name}/restore

    Roll the claim back to a point in time after a bad write.

  4. 4
    RotatePOST/api/v1/claims/{name}/rotate

    Rotate the credential; the app reads it as a Vault secret ref.

Architecture placement

Where it sits in the platform.

Databases & Data does not reimplement the platform — it composes it. These are the services it leans on and the seams between them.

DBaaS (SS-02)

ADR-0056: the only database plane — relational, document and vector engines as governed claims.

Prism (SS-09)

Contract-checked product analytics over the same tenancy model.

Mediation (SS-36)

Deterministic rating and reconciliation for high-volume usage data.

Vault (SS-05)

Custodies and rotates every database credential; the app never holds a raw secret.