A system bundle installs the catalogue and the simulator installs its own universe
Table of Contents
1. Summary
Every definition has one home. The market data service holds the catalogue: providers, sources, vendor instruments, mappings and rate cards. The simulator holds its generators and its universe. A system bundle installs both, in the system tenant and the system party. An adapter's announced universe is checked against the catalogue and never defines it.
2. Detail
2.1. Where each definition lives
| Definition | Home | Installed by | Changed by |
|---|---|---|---|
| Provider, source, rate card | ores.marketdata |
System bundle | System administrator |
| Vendor instrument and mapping | ores.marketdata |
System bundle | System administrator |
| Generator, collection, folder | ores.marketdata.synthetic |
System bundle | Simulator author |
| Simulator universe | ores.marketdata.synthetic |
System bundle (from the generators) | Simulator author |
| Subscription and route | ores.marketdata |
Profile or party administrator | Party administrator |
This table answers the question of where a feed is defined. The provider's feed is a set of catalogue rows. The simulator's way to produce it is a generator.
2.2. The universe check
At announce, the adapter sends its universe. The service compares it with the catalogue rows of its provider.
- An id in the catalogue and in the universe is served.
- An id in the catalogue and not in the universe cannot be demanded. The source screen lists it.
- An id in the universe and not in the catalogue is ignored and logged.
2.3. Why two homes
The service must own the catalogue because the mapping is the same for every source of a provider. The simulator must own its generators because only it needs them. A real adapter has no generators.
2.4. What the bundle holds
The bundle installs five providers: bloomberg, lseg, ice, tradeweb and ore. The data
format of each is on its own page, for example Bloomberg data format. The provider ore has three
sources of fixed ids: ore-import of kind replay, which the ORE import and the data quality
publish use; ore-simulated of kind simulated; and ore-derived of kind derived, which
the service uses for the values it computes, such as a bootstrapped curve. An observation
records the id of its source, and the series it lands in belongs to the provider.
2.5. The system bundle
The bundle publishes into the system tenant only. A tenant's own setup never writes the catalogue. A new tenant gets no market data rows, only subscriptions and routes.
3. See also
- Market Data Architecture — the structure note that orders this cluster.
- Every source belongs to a provider in the catalogue — completes: the rows the bundle installs.
- The simulator is one adapter plus the tools that author its generators — completes: the generators and the universe on the simulator side.
- Generators belong to the system tenant and the system party — completes: why the generators are system-owned.