Skip to main content
Version: 0.2.0 (Private Preview)

Control plane and data plane

Detailed Nexo architecture diagram. The SaaS control plane contains identity, environment, configuration revision, release, license, and operational-state services. An authenticated management channel connects desired state to the customer-hosted Manager, Kubernetes API, Operator, custom resources, and generated runtime. Separately, MongoDB driver traffic crosses the customer Service into Proxy ingress, request steps, routing, connection handling, MongoDB, response steps, and telemetry. Trust boundaries, failure isolation, Secret references, and planned Redis and PostgreSQL adapter boundaries are labeled.

Dashed arrows show desired-state and reconciliation flow, solid arrows show MongoDB traffic, and dotted arrows show status, telemetry, and the response path. MongoDB is available for licensed Private Preview evaluations. Redis and PostgreSQL remain Planned and are not implemented.

Diagram resources: Open the SVG full screen · Download the editable Excalidraw source

Control plane​

The control plane handles identity and tenancy, environment registration, configuration revisions, release orchestration, license state, and operational status. It produces approved desired state and receives runtime inventory and acknowledgements. It is not in the database application's request path.

Reconciliation sequence​

  1. An administrator or automation updates configuration through the Dashboard or Control Plane API.
  2. The Control Plane validates and versions the desired configuration or release target.
  3. Manager exchanges heartbeat inventory, approved commands, and acknowledgements over its authenticated management connection.
  4. Manager applies desired resources through the Kubernetes API.
  5. Operator build 20260611.352-008260c reconciles NexoProxy and its watched references, then renders the Proxy Deployment, Service, ConfigMaps, and referenced Secrets.
  6. Runtime and resource status returns through Kubernetes and Manager without becoming part of the application traffic path.

Data plane​

The data plane accepts MongoDB-compatible connections through the customer Service, decodes wire messages, selects the active pipeline, applies ordered request components, routes permitted traffic, manages the upstream connection, and processes the response. Metrics, logs, audit decisions, and health signals are observability outputs. Its availability and capacity directly affect applications routed through it.

Request and response sequence​

  1. A MongoDB-compatible driver connects to the customer-controlled Nexo Service.
  2. Proxy ingress decodes the message and selects the active validated pipeline.
  3. Request components can inspect, transform, allow, or explicitly reject the operation.
  4. Egress connects to NexoProxy.spec.targetAddress. The pinned runtime does not execute the rendered router or connection phases.
  5. MongoDB remains the system of record and returns the upstream response.
  6. Response components inspect or transform the result before it returns to the client.

Boundary behavior​

  • Publishing configuration and carrying database traffic are separate operations.
  • Loss of management connectivity must be evaluated independently from loss of database connectivity.
  • Operators should verify which configuration revision is active before and after a change.
  • Secrets should be supplied through the supported secret mechanism, not embedded in pipeline definitions.
  • The pinned Proxy controller does not watch NexoTrafficSplit, NexoTenantIsolation, NexoQuerySizeLimit, or NexoVersionCompat. After changing one of those resources, trigger reconciliation of the owning NexoProxy and verify the active graph revision.
  • The MongoDB adapter is the only supported 0.2.0 protocol path; Redis and PostgreSQL are Planned and are not implemented.

Document and test behavior for control-plane interruption, data-plane restart, upstream unavailability, and configuration rejection in your environment.

Search Nexo documentation

Type to search titles, headings, and page content.