Move from monolithic banking systems to decomposed services, microservices, modular recovery domains, and service-by-service survivability.
Pattern Description
Move from monolithic banking systems to decomposed services, microservices, modular recovery domains, and service-by-service survivability.
Signals / Evidence
Interview and framework signals: all-or-nothing banking systems force wide shutdowns; microservice design lets one service fail without stopping the whole bank. Handwritten framework also emphasized migration from monolith to services/microservices.
Risk Drivers That Made the Pattern Emerge
Monolithic core-banking failures; inability to isolate one failed service; broad customer disruption from narrow technical defects; cascade failure across tightly coupled systems.
Rate this pattern
How critical is this pattern to our continuity right now?
- 1
- 2
- 3
- 4
- 5
How mature are we on this pattern today?
- 1
- 2
- 3
- 4
- 5
Is this pattern relevant to our context?
- Yes
- Partially
- No