ORE Studio Messaging Protocol Reference
Table of Contents
All inter-service and client-server communication in ORE Studio uses NATS with JSON payloads. See ores.nats for transport details (request/reply pattern, subject naming convention, queue groups, JetStream).
Services
Each domain service owns a subject namespace. Click a protocol reference for the full list of subjects and message types.
| Service | Subject Namespace | Protocol 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 |
Useful Pages
- ores.nats — transport layer: request/reply, subject naming, configuration
- System Model — overall system architecture