ores.refdata.client

ores.refdata.client is a header-only library of consumer-side helpers for reference data. It hosts the convention-aware FX rate formatter used by every rate-display surface, and the currency_pair_convention_cache: an in-process, per-tenant cache of currency-pair conventions loaded over NATS and reloaded on changed events. Its registrar wires the warm-up and the changed-event subscription at service startup. Consumers are the market-data client and the removed market-data plugins. A load carries a Bearer token when the producer checks authorisation; pass an ores.iam.client-style token provider in that case.

• Domain types from ores.refdata.api: currency_pair_convention.
• NATS protocol messages from ores.refdata.api: the read_currency_pair_conventions_for_cache request/response pair and the currency_pair_convention_changed_event.

• C++ headers with the rate formatter, the tenant cache, and the cache registrar.

• service/cache/currency_pair_convention_cache.hpp — load() and lookup() per tenant.
• service/cache/currency_pair_convention_cache_registrar.hpp — warm_and_subscribe_currency_pair_convention_cache().
• presentation/currency_pair_rate_formatter.hpp — format_rate().

• ores.refdata.api — the domain and protocol types.
• ores.eventing — the changed-event types and the partitioned_cache primitive.
• ores.nats — the service client and subscription type.
• ores.logging — logger setup.
• Optionally, an ores.iam.client token provider for authenticated loads.

• ores.refdata — component group overview.
• ores.refdata.api — domain types and NATS protocol messages.
• ores.refdata.service — the NATS service the client helpers talk to.
• ores.refdata Messaging Reference — full NATS subject and message catalogue.
• Where should an entity-mirror cache live? — the placement rules for this cache and its registrar.