An industry is where the work happens. The environments inside it are how it runs.
Each industry has a page of its own, and each page sets out the environments inside it: the workloads in play, the shapes the data takes, and the parts of the layer that carry them.
Each industry is a destination of its own, and each one is described by its data: the environments inside it, the workloads in play, the shapes that data takes, and the parts of the layer that carry them.
PLOMID data layer
The operating environments inside this industry. Each is a variation on one problem: a measurement stream that never stops, and records that have to stay accurate beside it.
The environments this industry runs in. All of them write events continuously and answer questions about them afterwards, which is what makes the read path the hard part rather than the write path.
The environments in this industry, from the storefront to the last mile. Each one holds structured records and the documents that describe them, which is where the friction usually lives.
The environments in this industry, where a structured record and a document are almost always asked for in the same request and governed by the same access rules.
The environments in this industry. Every one of them is a fleet writing state continuously while a much smaller number of readers ask questions across it.
Three connected environments, drawn as one topology: where the system runs, who runs it, and how close to the source it has to sit.
The industry is context; the workload is the thing being solved. Three chains, read left to right, each ending on the solution that carries it.
Every industry page is described in this vocabulary. Eight of the nine are data models with their own surface on the platform; events are a workload shape rather than a model. The mark beside each one is the same mark used wherever that model appears.
Records, keys and joins
Documents and nested objects
Direct access by key
Measurements and events in time order
Location as a queryable dimension
Similarity and semantic retrieval
Relationships and traversal
Large assets with queryable metadata
Operational events as they happen
Derived from the industry set, not chosen for the page: the solutions referenced by the most industries, each one a page of its own.
Tell us what the environment produces, how fast it moves and who asks questions of it. We will map it to the workloads, the shapes and the parts of the layer that carry them.