Reference Data
Financial Market Reference Data
sd-financial-market-reference-data · bian-reference-data
A BIAN service domain in Reference Data. It applies the Catalog functional pattern to the Market Reference Data, with the Market Reference Data Directory Entry as its control record — one independent Spring Boot microservice on the platform's Cilium eBPF mesh.
View repository ↗The 162-domain platform ↗
Business DomainReference Data
Functional PatternCatalog
Asset TypeMarket Reference Data
Control RecordMarket Reference Data Directory Entry
USEWhat it is used for
Representative use cases for the Financial Market Reference Data service domain within a BIAN-aligned core-banking landscape.
- Serve golden-source Market Reference Data data to every other service domain with full audit history
- Synchronize Financial Market Reference Data records bi-directionally with the core banking system of record
- Provide point-in-time lookups for regulatory reporting and reconciliation
APIBIAN semantic API
The control record (Market Reference Data Directory Entry) is exposed through uniform BIAN action terms. Java 21 · Spring Boot 3, OpenAPI at /swagger-ui.html, health at /actuator/health.
| Method | Path | BIAN action |
|---|
| GET | /v1/service-domain | Service metadata |
| POST | /v1/market-reference-data-directory-entry/initiate | Initiate |
| GET | /v1/market-reference-data-directory-entry/{crId}/retrieve | Retrieve |
| PUT | /v1/market-reference-data-directory-entry/{crId}/update | Update |
| PUT | /v1/market-reference-data-directory-entry/{crId}/control | Control (suspend / resume / terminate) |
INTBackend integrations
The systems and standards a real deployment of Financial Market Reference Data would transact with.
- Core banking: Temenos Transact, Infosys Finacle, Mambu, Thought Machine Vault
- Market data: Refinitiv/LSEG, Bloomberg, SIX Financial
- Registries & identity: GLEIF (LEI), SWIFTRef, national ID/address validators (DigiLocker, Loqate)
RUNRun it yourself
Each service domain is its own standalone Spring Boot repository — clone and run in seconds, or deploy onto Kubernetes with the bundled Helm chart behind the Cilium mesh.
# run this service domain standalone
git clone https://github.com/Sreenivas-Sadhu-Prabhakara/sd-financial-market-reference-data
mvn -f sd-financial-market-reference-data spring-boot:run
curl localhost:8080/v1/service-domain
# or deploy onto Kubernetes (Cilium eBPF mesh)
helm upgrade --install sd-financial-market-reference-data ./helm -n bian-reference-data
FAQQuestions
What is the BIAN “Catalog” functional pattern?
A Catalog service domain maintains an authoritative directory or reference list, serving golden-source records to the rest of the bank. Financial Market Reference Data applies it to the Market Reference Data.
What is a BIAN service domain?
BIAN (the Banking Industry Architecture Network) decomposes a bank into independent service domains, each owning exactly one business capability. Financial Market Reference Data is the service domain for Reference Data; it manages the Market Reference Data Directory Entry and exposes it through standard BIAN action terms.
What business area does Financial Market Reference Data belong to?
Financial Market Reference Data sits in the Reference Data business area — the golden-source reference-data backbone that every other service domain reads from. It runs in the bian-reference-data namespace as one independent Spring Boot microservice.
Is Financial Market Reference Data production-ready?
It is an educational reference implementation: a real BIAN REST API over an in-memory store, ready to be filled with domain logic. It is not a live bank and is not affiliated with BIAN.
SEEIn the landscape
Financial Market Reference Data is one of 162 BIAN service domains on the platform. Explore the rest: