Reference Data
Information Provider Operation
sd-information-provider-operation · bian-reference-data
A BIAN service domain in Reference Data. It applies the Operate functional pattern to the Information Feed, with the Information Feed Operating Session 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 PatternOperate
Asset TypeInformation Feed
Control RecordInformation Feed Operating Session
USEWhat it is used for
Representative use cases for the Information Provider Operation service domain within a BIAN-aligned core-banking landscape.
- Serve golden-source Information Feed data to every other service domain with full audit history
- Synchronize Information Provider Operation 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 (Information Feed Operating Session) 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/information-feed-operating-session/initiate | Initiate |
| GET | /v1/information-feed-operating-session/{crId}/retrieve | Retrieve |
| PUT | /v1/information-feed-operating-session/{crId}/update | Update |
| PUT | /v1/information-feed-operating-session/{crId}/control | Control (suspend / resume / terminate) |
INTBackend integrations
The systems and standards a real deployment of Information Provider Operation 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-information-provider-operation
mvn -f sd-information-provider-operation spring-boot:run
curl localhost:8080/v1/service-domain
# or deploy onto Kubernetes (Cilium eBPF mesh)
helm upgrade --install sd-information-provider-operation ./helm -n bian-reference-data
FAQQuestions
What is the BIAN “Operate” functional pattern?
An Operate service domain keeps a piece of operational or technical capability running day to day. Information Provider Operation applies it to the Information Feed.
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. Information Provider Operation is the service domain for Reference Data; it manages the Information Feed Operating Session and exposes it through standard BIAN action terms.
What business area does Information Provider Operation belong to?
Information Provider Operation 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 Information Provider Operation 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
Information Provider Operation is one of 162 BIAN service domains on the platform. Explore the rest: