A party takes a provider's feeds through a subscription
Table of Contents
1. Summary
A subscription says that one party takes the feeds of one provider, with a set of rights, for a period. It is an entitlement. A party names the provider and never the source, because the route chooses the source. See A party routes to exactly one source for each provider. The party does not need to know whether the source is simulated, and it can look it up.
2. Detail
2.1. What a row records
| Column | Meaning |
|---|---|
tenant_id, party_id |
The consumer |
provider |
The provider whose feeds the party takes |
rights |
A set of display, non_display and derived. See Display, non-display and derived rights are modelled on the subscription |
valid_from, valid_to |
The period of the subscription |
enabled |
A suspend flag. Nothing is deleted. |
| Audit columns and version | The standard members |
The natural key is the party, the provider and the period. A tenant admin or a party admin can read the subscriptions. A person with the write permission changes them.
2.2. What a subscription allows
- The party can demand the items that map to instruments of the provider. A
demand outside the subscription is refused with
not_entitled. - The party gets a route to one source. See A party routes to exactly one source for each provider.
- The party's usage is metered against the subscription. See Usage is recorded as events and priced later.
2.3. The enabled flag is a suspend
Setting enabled to false closes the party's demand and stops delivery. The
service keeps the row and the party's stored series. Setting the flag to true
restores service without a new row.
2.4. Who sees what
A party sees only its own subscriptions. The system tenant sees all. The catalogue rows are readable by every party. See Every source belongs to a provider in the catalogue.
3. See also
- The market data path: a public fixing, a curve, a report — the structure note that orders this cluster, and where to read this page in it.
- Market Data Architecture — the structure note that orders this cluster.
- A party routes to exactly one source for each provider — completes: how a subscription finds its source.
- Display, non-display and derived rights are modelled on the subscription — completes: the rights a subscription carries.
- Usage is recorded as events and priced later — completes: how usage is attributed to a subscription.