Skip to main content
Version: 0.1.0-alpha.3 (alpha)

Cluster topology

This is the intended Phase 5 clustered topology. The current standalone Linux node uses one node process, local durable catalogs and a loopback RPC listener. Phase 2 delivers authenticated OCI transfers and trusted package admission without a cluster control plane. Cluster control, remote invocation, workload mTLS and PostgreSQL remain planned; guest state belongs to Phase 4 and durable workflows to Phase 6. See the roadmap. The extension's Docker/Kubernetes benchmarks run that same standalone product inside containers; they do not implement this control plane or establish production HA.

Planned control plane​

Two or more latent-control instances may share PostgreSQL and an OCI registry. They expose management APIs and distribute route snapshots. A custom consensus system is not required for the initial architecture.

Planned data plane​

Every latentd node can execute any compatible release it can retrieve, verify, prepare, and admit under its trust and placement policies.

Node identity​

Node and control communication requires mutually authenticated transport. The architecture supports SPIFFE-compatible workload identities but does not require a specific identity provider in the interface scaffold.

Remote invocation​

A remote call carries the exact revision ID, release digest, contract, function, route generation, principal delegation, trace context, remaining deadline, delegated resource budget, and idempotency information.

The receiving node must execute that exact release or reject the call. It may not silently substitute a newer route.

Availability​

Availability is expressed as eligible nodes and cached artifact copies rather than running replicas:

minimum cached copies
minimum zones
allowed trust classes
allowed architectures
required accelerators or CPU features

Node failure​

  • unstarted queued work may be re-routed,
  • stateless work may be retried only under retry policy,
  • uncommitted state is discarded,
  • committed state remains durable,
  • effect intents in the outbox remain durable,
  • entity leases expire,
  • workflow continuations remain persisted.