Operational time and sessions
Johannesburg schedules and European market hours can shift relative to each other when Europe changes seasonal time. Use explicit zones and source calendars rather than assuming a constant London-to-Johannesburg offset.
Market data · deployment planning
Market Data for Brokers in South Africa
Plan a market-data deployment for South Africa around the actual source, hosting route, instrument calendars and consumer requirements.
Regional acceptance checks
Test FX session transitions, weekend status and escalation outside the local support window. Currency coverage, redistribution permissions and route performance must be agreed for the actual sources and consumers.
Requirements to confirm
- Deployment city and hosting environment
- IANA zones: Africa/Johannesburg and Europe/London
- Per-instrument holiday calendars
- Measured route and incident ownership
Bring the proposed instrument list, source documentation and consumer workflow to a technical discussion. The agreed integration specification defines coverage, fields, usage permissions and acceptance tests.
Integration brief
A practical deployment brief for South Africa
| Operating location | Identify the actual hosting city and consumer location before selecting the delivery route. |
|---|---|
| Time zones | Africa/Johannesburg. Preserve source and archive timestamps in UTC. |
| Instrument calendar | Confirm the source calendar per instrument, including holidays and session breaks. |
| Acceptance evidence | Record the route, test window, clock synchronization and responsibilities for each layer. |
Separate location from instrument policy
A Johannesburg operating schedule and an upstream exchange calendar describe different things. Map both so application availability is not confused with instrument availability.
What to test
- Run acceptance tests during the intended consumer operating hours and across source reconnects. Capture UTC timestamps and ownership of source, normalization and downstream adapter incidents.
- Check that incident ownership covers the sessions your consumers use.
- Compare source event time with receive time rather than reporting an unexplained latency number.