Glossary
Plain-language definitions of the terms used across the Atlas documentation.
Terms are grouped by topic. Each links to the chapter that explains it in depth.
Core concepts
| Term | Meaning |
|---|---|
| Peer | A device or node that holds data and synchronizes it with other peers. |
| Local commit | A write that is durable on the device where it was made. It does not mean other peers have it. See storage and replication. |
| Replication scope | A name for the set of data that peers exchange. A matching name never grants access. |
| Capability | A signed command that authorizes one action on data. |
| Principal | The identity an application acts as. See identity and authorization. |
Platform data
| Term | Meaning |
|---|---|
| Entity | A value with a stable identity, a name, a lifecycle and type-specific data. |
| Group | Membership that merges across offline peers and carries proof of authority. |
| Schema | The field definitions, validation rules and merge behavior for a kind of data. |
| Document | Structured fields bound to a schema, with a lifecycle. |
| Blob | Binary content referenced by a content address. |
| Event | A bounded notification that something happened. Delivery is reported separately from acceptance. |
| Stream | A producer's continuing samples, received through a subscription the consumer owns. |
| Workflow | Transition definitions and the state derived from them. |
Mission
| Term | Meaning |
|---|---|
| Mission | The application layer built on Platform: organizations, admission, and domain models. |
| Organization | The top-level body that owns Groups, teams and sites. |
| Track | A stable identity for an observed object, with saved context. |
| Asset | An item or resource with a quantity, an owning team and a containing site. |
| Site | A geographic entity with a type and a lifecycle. |
Networking and operations
| Term | Meaning |
|---|---|
| Atlas Mesh | The peer-to-peer messaging layer. |
| Gateway | An always-on peer that keeps data available for peers that connect later. It is never required for two peers to exchange data. |
| Gateway Fabric | The architecture for running Gateways: carriers, a persistent peer runtime, and deployment roles. |
| Carrier | A network path that moves bytes or messages. Availability of a carrier does not grant access to data. |
Was this page helpful?