▚ BIAN PLATFORM Master Catalog GitHub ↗

A CORE-BANKING SERVICE LANDSCAPE · BIAN-ALIGNED · NETFLIX-STYLE

One bank.
162 service domains.
One paved road.

The full BIAN service landscape generated as independent Spring Boot microservices — one git repo each — deployed on Kubernetes behind a sidecar-free Cilium eBPF mesh, with seven domains carrying real, tested banking logic.

162service domains
(one repo each)
7deep domains
real rules + tests
5business areas
= 5 namespaces
0sidecars
(eBPF mesh)
2gates opened
Postgres · Kafka

01The end-to-end, in seven moves

Everything flows from one JSON file. Click each step.

02Architecture — click a layer

The Netflix lineage, modernized

Eureka→ K8s DNS
Zuul→ Cilium Gateway API
Ribbon→ eBPF service LB
Hystrix→ Resilience4j + mesh policy
Atlas→ Prometheus + Hubble
Paved road→ the generator

03Service Domain Explorer

Every BIAN service domain in the landscape — searchable. Each row is its own GitHub repo.

Service domainArea / domainPatternControl recordRepo

04The seven deep domains

Graduated from the template (.bian-graduated) — real rules, real tests, contracts owned per repo.

05Flagship flows — try them

💸 The payment saga Payment Order → Payment Execution → accounts

Money moves in two legs with compensation. Pick a scenario and step through:

🚨 Fraud scoring — live calculator

The exact rules running in sd-fraud-detection. Move the dials:

🪪 KYC decision pipeline

Screening precedence in sd-know-your-customer — toggle the facts:

06Phase roadmap & status

RUN running/verified · STAGED scripted & gated, one command to run · PLANNED designed in docs/PHASES.md

07Run it yourself

1 · Generate the landscape

git clone https://github.com/Sreenivas-Sadhu-Prabhakara/bian-platform
python3 bian-platform/generator/generate.py   # 162 repos from one catalog

2 · Bring up the platform

# kind + Cilium (CNI + mesh + gateway) + namespaces + policies
./bian-platform/scripts/bootstrap-cluster.sh

3 · Open the gates

CONFIRM_HYDRATE=yes ./bian-platform/platform-infra/postgres/hydrate.sh
CONFIRM_KAFKA=yes   ./bian-platform/platform-infra/kafka/install.sh

4 · Deploy a slice & hit the mesh

./bian-platform/scripts/build-all.sh  --only sd-current-account
./bian-platform/scripts/deploy-all.sh --only sd-current-account
kubectl -n bian-system port-forward svc/cilium-gateway-bian-gateway 18080:80 &
curl localhost:18080/sd-current-account/v1/service-domain

Rules of the road: never hand-edit generated boilerplate (fix the template, re-stamp) · the catalog is the API · deep repos graduate via .bian-graduated and are never re-stamped. Full ADRs in docs/adr.

08BIAN, explained

Short answers to what BIAN, service domains and the sidecar-free mesh actually mean.

What is BIAN?
BIAN (the Banking Industry Architecture Network) is a global not-for-profit that defines a standard reference architecture decomposing a bank into around 300 independent service domains, each owning a single business capability. This platform implements 162 of them as independent microservices.
What is a BIAN service domain?
A service domain is the smallest unit of business capability in BIAN — for example Payment Execution, Customer Offer or Fraud Evaluation. Each owns one control record and exposes it through standard BIAN action terms such as Initiate, Retrieve, Update and Control.
Why one microservice and one repository per service domain?
It follows the Netflix-style multi-repo model: each domain is independently owned, built, tested and deployed, so a team can ship one capability without touching the rest of the bank. This platform generates one Spring Boot repository per service domain.
What is the Cilium eBPF service mesh?
Cilium provides a sidecar-free service mesh using eBPF in the Linux kernel, giving identity-based network policy and observability between the service domains without the overhead of a per-pod proxy sidecar.
What are the “deep” domains?
Seven domains carry real, tested banking logic — such as the debit-credit payments saga — rather than scaffolding. The rest are Phase-1 BIAN-shaped scaffolds: a real REST API over an in-memory store, ready to be filled with domain logic.
Is the BIAN Platform production-ready?
No. It is an educational reference landscape, not a real bank, and is not affiliated with, endorsed by, or certified by BIAN (the Banking Industry Architecture Network).