ORE Studio Messaging Reference
All inter-service and client-server communication in ORE Studio uses NATS with JSON payloads. The transport library is ores.nats (request/reply pattern, subject naming convention, queue groups, JetStream). This page is the cross-service namespace index; each row links to the full subject inventory for that service.
Services
Each domain service owns a subject namespace.
| Service | Subject Namespace | Messaging Reference |
|---|---|---|
| ores.iam | iam.v1.> |
ores.iam Messaging Reference |
| ores.refdata | refdata.v1.> |
ores.refdata Messaging Reference |
| ores.variability | variability.v1.> |
ores.variability Messaging Reference |
| ores.assets | assets.v1.> |
ores.assets Messaging Reference |
| ores.telemetry | telemetry.v1.> |
ores.telemetry Messaging Reference |
| ores.dq | dq.v1.> |
ores.dq Messaging Reference |
| ores.trading | trading.v1.> |
ores.trading Messaging Reference |
| ores.scheduler | scheduler.v1.> |
ores.scheduler Messaging Reference |
| ores.synthetic | synthetic.v1.> |
ores.synthetic Messaging Reference |
| ores.reporting | reporting.v1.> |
ores.reporting Messaging Reference |
See also
- ores.nats — transport library: request/reply, subject naming, queue groups, JetStream.
- NATS — the upstream messaging technology this is built on.
- System Model — overall system architecture.
- cpp_messaging — the literate templates that generate the protocol facet.