In and Out: A 20-Minute Adventure or How to Rewrite a Bank's API Gateway
summary
A bank replaced its API gateway by identifying why the existing system no longer fit, selecting and comparing appropriate tools, and preparing Go applications for the migration. The talk covers using Go-specific performance profilers and load-testing practices to guide the rewrite and ensure the new gateway meets operational needs.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:49Why API Gateway
- 3:39Old solution problems
- 8:17Rewriting the Gateway
- 11:08New solution requirements
- 13:57Fast HTTP and Go
- 15:20Compilation and optimization
- 17:48Gradual migration
- 20:39Implementation issues
- 23:27Results and benefits
- 24:08Conclusion and recommendations
- 25:11Q&A
related talks
31mIn and Out in 20 Minutes: How We Rewrote a Bank's API Gateway
26mAPI Gateway, A Success Story
23mLessons from Building an API Management Platform
43mBuilding an API Gateway to Escape the Monolith: The Strategy
36mOne to millions - opportunities and challenges in scaling APIs.
26mEvolving Your API
45mGrowing at the Edge: Doubling Traffic While Changing the API Gateway
31mOpen Banking APIs and Architecture at Scale