Every source belongs to a provider in the catalogue
Table of Contents
1. Summary
A provider is a vendor, an exchange, a broker or a reference set, and it owns
a namespace of ids. The catalogue holds the providers, their sources, their
vendor instruments and their mappings. It lives in ores.marketdata. The
system tenant owns it, and every tenant can read it.
2. Detail
2.1. The provider row
| Column | Meaning |
|---|---|
code |
The provider code in lower case, such as bloomberg, lseg, ice, ore or demo |
name |
The provider as a person knows it |
kind |
data_vendor, exchange, broker or reference |
description |
What the provider supplies |
display_order |
The order screens list providers in |
The name carries no mark of any source kind. Bloomberg is Bloomberg whether the source is live or simulated. The kind is a property of the source. See The source kind.
2.2. What else the catalogue holds
- Sources of each provider. See The source kind.
- Vendor instruments of each provider. See A vendor instrument is an id scheme, an id and a field.
- Mappings from vendor instruments to internal items. See The mapping belongs to the provider and not to the source.
- Rate cards of the sources. See A rate card on the source turns usage into a bill the platform shares.
2.3. Who owns it and who reads it
The system tenant and the system party own all catalogue rows. Row-level security lets every tenant read them, and only the system tenant writes them. A party therefore sees every provider and source and can look up what each source is.
2.4. How it is installed
The system bundle installs the catalogue. See A system bundle installs the catalogue and the simulator installs its own universe.
2.5. Two views of one provider
A provider can have many sources at once. Bloomberg can have bloomberg-a
and bloomberg-b. A source name says the provider and the instance, and never the kind. A party subscribes to the provider and the route picks the
source. See A party takes a provider's feeds through a subscription and A party routes to exactly one source for each provider.
3. See also
- Market Data Architecture — the structure note that orders this cluster.
- The source kind — completes: the kind of each source.
- A vendor instrument is an id scheme, an id and a field — completes: the ids a provider publishes.
- A system bundle installs the catalogue and the simulator installs its own universe — completes: how the rows arrive.