Free practitioner guide (PDF)
The orchestration-layer pattern for core banking integration
One architectural pattern for the seam between a bank's channels and its heterogeneous back end: a middle-tier orchestration layer, one encapsulating service per legacy system, and collect-then-distribute for long, multi-step flows. Two anonymised field examples, when to use the pattern and when not, and a build checklist - mapped to the DORA, RTGS renewal and ISO 20022 record.
What is inside
- The pattern: a middle-tier orchestrator, a thin backend-for-frontend, one wrapper per legacy system, state in a document store
- Two worked examples from the field, generalised - heavy branching, and a ten-plus-step collect-then-distribute flow
- When to use the pattern, and the cases where its cost is not repaid
- Each seam-level failure on the public record mapped to a specific part of the pattern
- A build checklist, plus two field notes on seam ownership and rollback discipline
For integration architects, delivery leads and engineers who own the space between the customer-facing channels and a bank's heterogeneous back-end systems.