Adopting a Modern API Strategy for Hybrid, Multi-Cloud Architectures
summary
Argues for a pragmatic, incremental ice cream scoop approach: extract the smallest painful business domains first, avoid full rewrites. Recommends introducing an API gateway as the edge routing and versioning layer from day one, duplicating a portion of production traffic for safe rollouts. Treat networking as first-class by deploying sidecar proxy data planes per instance and a centralized control plane for configuration and observability; Kong and nginx are cited as concrete implementations for that control/data plane split.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:23Monoliths replaced today
- 3:13Business case for microservices
- 5:42Transition from monolith?
- 7:32Organizational readiness
- 8:17Monolith decomposition strategies
- 10:01Ice cream scoop strategy
- 13:56Routing traffic during transition
- 15:25API gateways in modernization
- 17:34Hybrid and multi-cloud realities
- 19:19Microservice sizing
- 20:44Network reliability challenges
- 22:49Service mesh role
- 25:56Control plane vs data plane
- 27:02Recap and key takeaways from the journey
- 28:26Q&A
related talks
34mArchitektury Aplikacji: The last mile of microservices
23mDecentralized API Management for Agile Enterprises
21mPragmatic Strategies for Global API Integration
27mMaster API Gateways: Boost Your Microservices Strategy
27mEnterprise API management in agile integration
48mRefactoring of REST API
19mMastering Multi-API Gateways: Strategies for Scale, Security & Success.
23mLeverage APIs to Transform Your Business Landscape