Future Ready Open Banking Architecture
summary
Argues that the optimal open banking stack today pairs Kubernetes microservices with a service mesh so each API gets independent deploy/scale and cross‑cutting concerns live in Istio/Envoy sidecar proxies managed by a control plane, not embedded libraries; perimeter traffic remains a lightweight perimeter gateway (F5, nginx, HAProxy) for north‑south, while the mesh controls east‑west, easing legacy integration by fronting mainframes with proxies; warns serverless is immature for enterprise and says regulatory regimes force API management work while market‑driven banks focus on CI/CD speed.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:09Banking Evolved Banks are transforming into technology companies
- 1:59The Rise of the API APIs are the pipelines that power Open Banking
- 5:18Architecture Focus Regulations drive APIs, but markets drive speed
- 8:39The Role of API Gateways Beware the "Magical Black Box" approach
- 10:25Microservices Explained APIs & microservices are not the same
- 13:46MSA Roadmap Microservices Architecture (MSA) is evolving rapidly
- 17:34Optimal Architecture The service mesh is perfect for Open Banking
- 20:56Bank of the Future Success is a technological & cultural balancing act
- 23:09Build for Change Open Banking demands systems that can evolve
- 24:39Customer First Open Banking leads to authentic client relationships
related talks
27mBuilding API Infrastructure in a Decentralized World
41mBuilding a Bank (with DDD, Microservices, and Autonomous Teams)
31mOpen Banking, Open Source, and Open Standards
28mAn Open Source Architecture for Modernizing Market Risk Managem...
57mForking the Future: Embracing Microservices Evolution
22mUnlock Kubernetes & Envoy: Master Your API Ecosystem!
24mTransform Your Network: Master API Control & Security
31mThe API in 2017