Open Banking APIs and Architecture at Scale
summary
A large Southeast Asian bank migrates a Java monolith (one instance held 128 GB of RAM) into standardized microservices and completes the initial rollout in 3 months. The stack uses gRPC + Go, an API gateway, GitLab CI/CD and Kubernetes so teams push with a single git command, JWT scopes enforce access, no downtime occurs, CPU and memory density improves and hardware refresh costs fall while external partners can consume the same APIs.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:44Open Banking and Digital Transformation
- 5:33Initial Architectures
- 10:45Test-Driven Development
- 12:45Standardize Their Deployment Environments
- 15:36Kubernetes
- 27:01Conclusion
related talks
45mGrowing at the Edge: Doubling Traffic While Changing the API Gateway
51mMicroservices and Microfrontends: Scaling, Learning, Growing
31mIn and Out: A 20-Minute Adventure or How to Rewrite a Bank's API Gateway
45mHow we rebuild a legacy monolithic platform at CERN and still sleep at night
30mBanking on Cloud Foundry Platform: A Case Study of Digital Business Banking Applications
18mMicroservices Out In the Wild
26mBuilding a sustainable digital bank
30mMigrating a monolith to Cloud-Native and the stumbling blocks