The Broken Promise of API Management in Open Banking
summary
API management does not deliver open banking because gateways are treated as plug‑and‑play while back ends remain strictly consistent legacy cores, causing two real outages when mobile/query volume spikes overwhelm accounting ledgers; teams tack on replicated relational DB as comms or ESBs and later drift to eventual consistency to survive. Policy and grant enforcement stay weak, catalog/UIs act like CMSs, and hardware security modules refuse some gateways (HSM incompatibility), so many implementations miss regulatory deadlines or require major re‑architecture.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:42Regulatory Standards
- 3:24Metric Units
- 4:26Channels
- 5:46Oversimplification
- 9:19Transformational Program
- 10:48Integration
- 11:13API Gateway
- 11:46ESB
- 12:07The Problem
- 13:53Orchestration
- 14:45Distributed Systems Architecture
- 21:07Replication
- 21:54Skip this
related talks
24mThe Future of Open Banking: Key Trends & Challenges
48mThe Death of API Management. Welcome to the Funeral
26mOpen Banking and Open Insurance: The Role of APIs and Microservices
15mThe value of a flexible API Management solution for Open Banking.
27mEnterprise API management in agile integration
37mIntroduction to essential elements of Open Banking Framework
23mOpen Banking: The 3rd Channel
26mMastering API Strategies for Digital Transformation