Runtime-To-Runtime Transport Matrix¶
| Surface | What it does | Best for | Not for | Docs |
|---|---|---|---|---|
discovery |
advertises and finds runtimes on a LAN | first contact, browsing peers, pairing bootstrap | deterministic data exchange by itself | Discovery And Pairing |
zenoh / mesh |
shares explicit published values and subscriptions | multi-runtime data sharing on a plant network | same-host HardRT contracts | Mesh And Zenoh |
realtime |
same-host bounded shared-memory transport | tightly coupled low-latency paths | WAN or generic IP mesh | Realtime T0 |
web / runtime-cloud |
browser/fleet control plane, preflight, dispatch, rollout | federation, topology, remote operations | replacing deterministic data transport | Runtime Cloud Federation |
Recommended decision order¶
- Start with
discoveryif you are still finding peers or bootstrapping trust. - Use
zenohmesh when the goal is selective runtime-to-runtime data flow. - Use
realtimeonly when you explicitly need same-host deterministic transport. - Use runtime-cloud/web when the problem is orchestration, rollout, or fleet visibility rather than raw signal sharing.
Security boundary¶
connect/ answers how you wire runtimes together. operate/ answers how you
run them once they are connected.
- setup and exposure decisions: Security
- day-to-day federation/operator work: Operate -> Runtime Cloud