Choosing a new platform is only one decision in a banking modernization program. The harder discussion concerns how the existing and target systems will operate together.
GeekyAnts’ analysis of core banking modernization examines dependency mapping, authoritative data ownership, reconciliation, and gradual migration.
Five companies, different approaches
- GeekyAnts: Progressive modernization with explicit migration and validation controls.
- Accenture: A mix of strategies, including in-place optimization, read-workload offloading, and platform coexistence.
- IBM: Incremental application enhancement and integration between mainframes and cloud services.
- TCS: Workload-specific combinations of offloading, rehosting, re-engineering, and cloud adoption.
- Thoughtworks: Business-aligned increments that progressively separate capabilities and integrations.
This is a comparison of published approaches, rather than a performance ranking.
What would make an architecture proposal convincing?
A useful technical review could request three concrete artifacts:
- A dependency map for the first proposed change.
- Evidence showing how the target implementation will be evaluated.
- An operating plan assigning responsibility for cutover and recovery.
Those artifacts make competing proposals easier to assess against the same workload.
A proposal should also explain its trade-offs. Keeping existing technology may preserve constraints; introducing new services creates additional operational responsibilities. The architectural choice needs a business reason and a team capable of operating it.
Top comments (0)