Skip to content

truST Documentation

Overview

johannesPettersson80/trust-platform

Runtime To Runtime¶

flowchart LR
    A[Runtime A] -->|discover and pair| B[Runtime B]
    A -->|mesh / Zenoh data flow| B
    A -->|realtime T0 on same host| B
    A -->|runtime-cloud federation| C[Cloud / fleet control plane]
    C --> B

Figure: Runtime-to-runtime work spans local discovery, sustained mesh exchange, same-host realtime transport, and fleet/cloud coordination.

Start Here¶

Transport Matrix: compare discovery, mesh, realtime, and runtime-cloud paths before you configure anything

Choose By Goal¶

Goal	Page
discover nearby runtimes and pair them	Discovery And Pairing
share data across a distributed runtime mesh	Mesh And Zenoh
keep communication local and low-latency on one host	Realtime T0
coordinate runtimes across sites or fleets	Runtime Cloud Federation
understand exposure and hardening boundaries	Security

Rule Of Thumb¶

Use discovery when you are still finding peers on a local network.
Use mesh when runtimes need sustained data exchange.
Use realtime T0 when the runtimes share a host and latency matters more than distribution.
Use runtime-cloud federation when the system boundary is larger than one local network.