A source switch changes one route and nothing else
Table of Contents
1. Summary
A party changes its source by changing one route. The service writes an audited, effective-dated change, sends new demand sets to the two adapters, and closes and opens the metering intervals. The party's series, its mapping and its consumers do not change.
2. Detail
Figure 1: Switching a party from the simulated source to the live source.
Source: market_data_source_switch.puml. Regenerate with
plantuml -tpng doc/knowledge/architecture/market_data_source_switch.puml.
2.1. The steps
- The party administrator writes a new route with an effective date and a reason.
- The service checks the subscription, the rights and the state of the new source.
- The service closes the old metering interval and opens the new one.
- The service sends the old adapter a demand set without the party's ids and the new adapter a demand set with them.
- Ticks of the new source reach the same series. Each observation records its source.
2.2. What does not change
- The series key (item, provider, party).
- The mapping.
- Every consumer.
2.3. What a reader sees
The series page shows the source of each value. The history of the route shows who changed it, when and why. Prices from the two sources can differ at the switch. That is a market fact.
3. See also
- Market Data Architecture — the structure note that orders this cluster.
- A party routes to exactly one source for each provider — completes: the entity that changes.
- A quote series is keyed by item, provider and party — completes: why one series survives the switch.
- Demand drives what an adapter publishes — completes: the demand sets that move.