Atlas Gateway Fabric architecture
Understand Gateway Fabric carriers, its persistent Mission peer runtime, and optional deployment roles.
Atlas Gateway Fabric keeps authorized Mission state available for peer synchronization and permitted forwarding. Run it as a persistent service with a provisioned identity.
How peers use Gateway Fabric
A field device saves an observation while another device is offline. Gateway Fabric receives that state when connectivity permits. The second device later synchronizes through an available authorized peer. The original local save does not wait for Gateway Fabric.
Separate carriers from the operational peer
| Layer | Responsibility | Authority boundary |
|---|---|---|
| Transport carriers | Carry bytes or topic messages through allowed network paths | Carrier availability does not grant data access |
| Authenticated protocol sessions | Identify peers and exchange control and synchronization messages | Verify the peer and each requested scope |
| Mission operational runtime | Load durable identity, install organization credentials, open storage, and serve Mission gateway protocols | Apply organization and protected-content permission checks |
| External adapter | Translate an authenticated external protocol into application data | Validate the external source and the adapter's own publishing authority |
The carriers remain domain-neutral. A WebSocket carrier transports encrypted multiplexed streams. MQTT supplies a topic-based carrier with signed CONNECT identity and topic authorization. Neither carrier interprets sensor observations as Mission Tracks.
The whole Gateway Fabric process is not a stateless relay. Its Mission-backed runtime opens persistent storage, installs its provisioned credentials, registers organization synchronization, and maintains authorized state. Protect its host and recovery set accordingly.
A transport relay carries encrypted traffic when an allowed direct path is unavailable. It does not supply Mission organization membership or act as the Gateway Fabric database.
Connections and protocol planes
WebSocket binary messages carry Noise-encrypted traffic. A multiplexer supplies logical bidirectional streams over the socket. Each stream identifies the control or operation-log plane before protocol processing. Control requests and operation-log synchronization retain their own framing and authorization.
QUIC networking remains distinct from the executable's selected client-facing uplink. The executable requires ws with [transport.ws] enabled. Enabling MQTT starts its broker, not an MQTT control-uplink acceptor. The configuration reference explains supported selections and defaults.
A configured listener does not establish support for every live stream mode. Match the peer's protocol, transport capabilities, feature profile, and routing policy. Do not infer a REST ingestion API from a listener or product name.
Choose where Gateway Fabric belongs
Use Gateway Fabric for persistent Mission availability, operational reachability, and permitted forwarding. Direct authenticated peers can communicate without a mandatory Gateway Fabric hop.
An independent Platform application uses its own schemas, identities, capabilities, and protocols. It can run an always-on Platform peer without Mission admission or Gateway Fabric. Reusing a domain-neutral carrier does not enroll that application in Mission. Start with Platform transports for that topology.
Keep durable and live outcomes independent
| Data path | Gateway Fabric role when selected by policy | Consumer responsibility |
|---|---|---|
| Saved entity state | Persist and synchronize authorized received state | Resolve saved context independently of live delivery |
| Event notification | Participate in an allowed forwarding path | Verify authority and freshness, deduplicate, and handle bounded observations |
| Live telemetry | Participate only when the permitted stream route includes it | Open an independently authorized subscription |
A Track publisher saves locally, optionally advertises telemetry, and publishes a detection with the entity reference and optional stream reference. It does not wait for remote replication. The database does not automatically archive every sample or missed notification.
Platform owns events, streams, and replication. Gateway Fabric does not redefine receiver lifetime, promise replay, or provide a numeric latency guarantee.
References and concepts
- Configuration reference defines commands, fields, defaults, and listener constraints.
- Integration boundaries defines adapter ownership and independent data paths.
- Mission identity and admission defines service identity and organization authority.