Unified data infrastructure
GitHub Let's talk

Edge Infrastructure

Regions, nodes and placement as one topology.

Edge is a placement question: some reads have to happen next to the equipment, and the record still has to be complete somewhere.

See Edge Computing All of Public & Sovereign

A local answer, a complete central record, and the reconciliation stated between them.

The story

A local answer, a complete central record, and the reconciliation stated between them.

Where it starts

Local telemetry

Readings buffered close to the equipment. It is the first of 4 workloads running in Edge Infrastructure.

The question it raises

Local read, central record

A site answers its own questions while the durable history stays in one place.

Why one question is hard

From Acquire to Retain centrally

Edge Infrastructure data moves through 4 stages — Acquire → Decide locally → Synchronise → Retain centrally. The shapes in play are Time series, SQL, JSON / documents, Events, and answering one question means reading across all of them.

What PLOMID contributes

Edge is where the deployment fabric matters most, and where it is least finished. Both are stated here.

  • Deployment is a decision Self-hosted, edge and managed topologies are design destinations of the deployment fabric, and the fabric is specified as its own part of the platform.
  • Control over operation Who runs the system, and where it runs, is part of the first conversation rather than a tier on a pricing page.
  • Time-ordered storage Measurements and events are stored beside the records and documents they describe, so history and current state agree.
The environment

Compute and data close to the source, with a central record behind it.

Edge deployments need a small footprint, local reads and a defined relationship to the central system. PLOMID is one system with one storage contract, so the shape of an edge topology is legible, but the fabric that distributes it is direction and is marked as such here.

Deployment & residency

Where this data is allowed to run.

On constrained hardware near the equipment, with a central system holding the durable record.

Deployment, residency and control
The data journey

How edge infrastructure data reaches one layer.

Walk the path the data takes, from the environment that produces it to the questions it answers. Select a station, or a shape, to read each step.

A local answer, a complete central record, and the reconciliation stated between them.

Environment

The site

Constrained hardware near the equipment, on a link that drops.

Time series

One environment · many workloads

What runs against edge infrastructure data.

4 workload families over one set of shapes. Choose one to see what it moves and where it lands.

Readings buffered close to the equipment.

  • Planned once against the layer, not once per store
  • Read beside the records it shares a key with
  • Persisted under one storage contract
Where the data goes to work

Questions asked inside the boundary.

Each one is answered where the environment allows, from the same layer rather than a copy that drifted.

Local read, central record

A site answers its own questions while the durable history stays in one place.

  • Time series

Reconciliation stated

Synchronisation events are data, so a discrepancy is visible rather than silent.

  • SQL
  • JSON / documents

Constrained footprints

One storage contract keeps the edge component describable instead of a separate product.

  • Events

Deployment as policy

Where a workload runs becomes a declared decision, which is the direction the fabric is being built toward.

  • Time series
  • SQL
Data models in play

The shapes, in one layer.

4 shapes carry this domain. Choose a stage to read the operation, or a shape to see every stage that handles it.

PLOMID · Edge Infrastructure acquire · decide locally · synchronise · retain centrally Select a stage
Stage

Acquire

Readings taken at the equipment

Time series

Workload map Edge Infrastructure workload map. Every shape on it is a surface of the layer, and each stage names the part of the operation it carries.
  • Time series Measurements and events in time order
  • SQL Records, keys and joins
  • JSON / documents Documents and nested objects
  • Events Operational events as they happen
Workload architecture

The boundary, then the path.

The environments set what the architecture may do — then the work, the shapes and the path a request takes.

Edge Infrastructure · workload architecture
Workloads

What runs against this data.

  • Local telemetry
  • Local records
  • Sync and reconciliation events
  • Central history
Data models

The shapes those workloads read and write.

  • Time series
  • SQL
  • JSON / documents
  • Events
The layer

One path from a request to the data it names.

  • Planning Predicates narrow the work before it runs
  • Execution Records, fields and windows answered together
  • Transactions Readers and writers do not block each other
Surfaces

How the work reaches the layer.

  • SQL surface The query language the layer is documented in
  • Applications Services and jobs writing and reading as they run
  • Analytics & AI clients The same layer, the same access path
What you build next

Edge Computing

Data and reads close to the source, with one durable record behind them.

If Local read, central record is your question, start here.

See Edge Computing Every solution
Next

Where to go next

Solutions The workload answers this industry leans on, with their models and status. Platform The data models in the product today, and the ones extending the layer. Architecture How a request is planned, executed and persisted once it reaches the layer.