Enterprise & Commerce
Records, documents and events around a customer.
The commercial picture is assembled from customers, orders, stock, shipments and the signal trail around them. Each of those lives in a different system today, and the join between them is the work.
Records, documents and events around a customer.
What runs when a customer acts.
Start with the work: orders, shipments and commitments drawn from every environment here. Choose one to see the shapes it moves and where it lands.
Customers, suppliers, products, sites and organisational structure. — Enterprise
- Planned once against the layer, not once per store
- Read beside the records it shares a key with
- Persisted under one storage contract
Agreements, correspondence, policies and technical documentation. — Enterprise
- Planned once against the layer, not once per store
- Read beside the records it shares a key with
- Persisted under one storage contract
Approvals, handovers, workflow transitions and audit events. — Enterprise
- Planned once against the layer, not once per store
- Read beside the records it shares a key with
- Persisted under one storage contract
Operational and management reporting over live data. — Enterprise
- Planned once against the layer, not once per store
- Read beside the records it shares a key with
- Persisted under one storage contract
Sales lines, tenders, returns and channels as records. — Retail
- Planned once against the layer, not once per store
- Read beside the records it shares a key with
- Persisted under one storage contract
Receipts, transfers, counts and shrinkage as events. — Retail
- Planned once against the layer, not once per store
- Read beside the records it shares a key with
- Persisted under one storage contract
Sites, shelves, products, suppliers and price history. — Retail
- Planned once against the layer, not once per store
- Read beside the records it shares a key with
- Persisted under one storage contract
Footfall, dwell, queue and promotion response. — Retail
- Planned once against the layer, not once per store
- Read beside the records it shares a key with
- Persisted under one storage contract
Where this industry runs.
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.
- Enterprise Systems of record, documents, workflow events and reporting in one organisation.
- Retail Transactions, stock, stores, promotions and customer behaviour.
- E-commerce Orders, catalogues, inventory, sessions and fulfilment events.
- Logistics Shipments, routes, positions, scans and delivery events.
- Supply Chain Suppliers, orders, inventory, movements and the documents between them.
- Telecom Network topology, performance counters, subscriber records and incidents.
From the customer event to the record around it.
Records, documents and events around a customer, kept in one place. Four readings of the same system: the scenario first, then the environments it spans, the shapes the data takes, and the work they support.
The contexts this industry runs in.
- Enterprise Systems of record, documents, workflow events and reporting in one organisation.
- Retail Transactions, stock, stores, promotions and customer behaviour.
- E-commerce Orders, catalogues, inventory, sessions and fulfilment events.
- Logistics Shipments, routes, positions, scans and delivery events.
- Supply Chain Suppliers, orders, inventory, movements and the documents between them.
The shapes the data takes across them.
- SQL Records, keys and joins
- JSON / documents Documents and nested objects
- Objects Large assets with queryable metadata
- Events Operational events as they happen
- Time series Measurements and events in time order
Where the shapes stop being separate systems.
- One plan per request
- Snapshot reads under continuous writes
- One storage contract
The questions asked across the industry.
- One question, one query
- Documentation stays findable
- Audit trail
- Fewer integration surfaces
One layer holds these shapes at once, which is what removes the copy between them: an event, the record it belongs to and the document around it are read from the same place, whichever environment is asking.
Which workload touches which model.
The same relationship every industry page uses: the work, the shapes it names, and the path a request takes to reach them. Only the names change with the industry.
What runs against this data.
- Master and reference data
- Documents and contracts
- Process events
- Reporting aggregates
- Transactions and baskets
The shapes those workloads read and write.
- SQL
- JSON / documents
- Objects
- Events
- Time series
- Geo
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
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
The parts of the layer this industry leans on.
Counted across the environments above rather than chosen for this page: the properties every environment in this industry depends on, and the workload answers they keep returning to.
- One data layer Rows, documents and time-ordered events live in one system, so a question is asked once instead of once per store.
- 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.
- Time-ordered storage Measurements and events are stored beside the records and documents they describe, so history and current state agree.
- Predicates narrow the work Indexes and access paths decide what a query touches before a page is read, so operational reads stay bounded.
- Every client, one layer Applications, AI clients, services and background jobs reach the same data through the same interfaces.
- Documents beside rows Fields that keep changing shape stay queryable instead of being exported into a separate document store.
Solutions this industry keeps returning to.
Derived from the industry's own environments: the solutions referenced by the most of them, each one a page of its own.
- Operational Analytics → Reporting that reads the operational source instead of a copy of it. Referenced by 6 of 6 environments.
- Real-time Analytics → Windows and aggregates over data that is still being written. Referenced by 4 of 6 environments.
- Transactional Systems → Application records with consistent reads and writes while reports run against them. Referenced by 3 of 6 environments.
- IoT → Device fleets: identity, telemetry, current state and lifecycle events. Referenced by 3 of 6 environments.
- Edge Computing → Data and reads close to the source, with one durable record behind them. Referenced by 3 of 6 environments.
- Data Infrastructure → One layer for records, documents and time-ordered data, instead of one system per shape. Referenced by 2 of 6 environments.
- EnterpriseSystems of record, documents, workflow events and reporting in one organisation.
- RetailTransactions, stock, stores, promotions and customer behaviour.
- E-commerceOrders, catalogues, inventory, sessions and fulfilment events.
- LogisticsShipments, routes, positions, scans and delivery events.
- Supply ChainSuppliers, orders, inventory, movements and the documents between them.
- TelecomNetwork topology, performance counters, subscriber records and incidents.
One customer, one record.
Tell us which storefronts, warehouses and routes you run and who asks questions of the data. We will map them to the workloads, the shapes and the parts of the layer that carry them.