Availability with cause
A stock-out is read with its movement events and its transaction history in one request.
- SQL
A stock-out explained from its own movement events, while the store is open.
Where it starts
Transactions and baskets
Sales lines, tenders, returns and channels as records. It is the first of 4 workloads running in Retail.
The question it raises
Availability with cause
A stock-out is read with its movement events and its transaction history in one request.
Why one question is hard
From Assort to Measure
Retail data moves through 4 stages — Assort → Supply → Sell → Measure. The shapes in play are SQL, Time series, Events, JSON / documents, and answering one question means reading across all of them.
What PLOMID contributes
Retail reads are transactional and analytical at once. These are the parts that let one system serve both.
- One data layer Rows, documents and time-ordered events live in one system, so a question is asked once instead of once per store.
- 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.