Eighteen workloads, one layer underneath.

Every answer here starts from the work, not from the tooling.

What a developer is doing with the data, and which PLOMID data models carry it. Behind each one: the architecture, the shapes the data takes, and the industries where the same shapes appear.

4 families · 18 workload answers
Data foundation Intelligence Industrial & operational Trust & deployment

One data layer

Four families, one layer. The shapes differ; the system underneath does not.
Solutions

Four families of workload.

Each solution names the models it depends on and the industries that run it, so the decision starts from the work rather than from a product list.

Data foundation

5 solutions

Records, documents and events in one layer.

Intelligence

6 solutions

Retrieval, search and AI over the same data.

Industrial & operational

4 solutions

Physical systems, equipment and their history.

Workload patterns

What could PLOMID solve?

Each pattern names the models it leans on. A model still being built keeps the dashed frame here, exactly as it does wherever it appears.

Application data

One record, read whole: its rows, its documents, and the history behind them.

One request reads rows, keys and joins alongside nested documents and the change history behind them, instead of loading one side into the other.

  • Rows for core records
  • Documents for changing shape
  • History read beside both
SQL + JSON + Time series Models in play
Data Infrastructure

Real-time data

What is happening now, to which record, and what led here.

Telemetry and events are stored with the records and documents they describe, so a window, the entity behind it and its context are read from one layer.

  • Events and measurements
  • Windowed reads with the record attached
  • No export between systems
Time series + SQL + JSON Models in play
Real-time Analytics

Operational reporting

Today's number, asked of live operations — filtered by the fields that don't fit columns.

Aggregates and windows run over the live tables with document fields filterable beside them, so the number you report and the number you serve come from one place.

  • Aggregates in place
  • Document fields filterable
  • One copy of the truth
SQL + JSON + Time series Models in play
Operational Analytics

Search and retrieval

Find what is similar — ranked, filtered by structure, and current as of the last write.

Embeddings are stored beside the records and documents they describe and ranked with distance ordering, filtered by structure, so similarity is an access path over the data that already serves the application.

  • Dense vector columns
  • Exact top-k, HNSW at scale
  • Metadata filtering beside ranking
Vector + SQL + JSON Models in play
AI Retrieval

Connected data

What is reachable, and what depends on what.

Questions about relationships rather than records: expressing edges directly removes the reconstruction at query time.

  • Nodes and edges as structures
  • Traversal without rebuild
  • Over data already in the layer
Graph Models in play
Knowledge Systems

Large objects

Files, media and artifacts that need to be found by query.

Objects are usually stored somewhere and described somewhere else. Keeping both in the layer means an asset is found by a query, not a convention.

  • Big immutable objects
  • Queryable metadata
  • No separate catalogue
Blobs Models in play
Document Intelligence
How to choose

Three things hold across every pattern.

Whatever you are building, the same three properties decide whether one layer makes it simpler.

Start from the workload
Each pattern names the work being done — the writes, the reads, the questions — and the data models that carry it, so the first decision is about the workload, not the tooling.
One layer, several shapes
Records, documents and time-ordered data live in one system, which is what removes the copies between them and the jobs that keep copies honest.
Architecture you can read
Every pattern resolves to the layer underneath it: the data models, the path a request takes, and the industry settings where the same shapes appear.