The architecture of an API platform
summary
46elks builds a European cloud communications platform that combines voice SMS MMS in one API, launched 3.5 years ago and exposed as a JSON API. Architecture starts as a tiny prototype and grows into load balancers, message buses, workers, databases and redundant carrier couplings across backup datacenters. Operational stack includes Nginx SSL offloading and Python + gevent for back ends. Key decisions: versioning, JSON, select vendors carefully, and choose consistency versus reliability per feature.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:16The essence of an API
- 4:37DATA ACCESS - Self contained
- 5:10SIDE EFFECTS - Self contained
- 8:20The golden rule of API design
related talks
42mThe future of API (Platform) architecture
48mTransforming a monolith to an API platform
27mAPIs beyond datacenters: Architecture and Best Practices
30mBuilding an API-enabled Open source stack - Strategy, Struggle & Success
23mAn Operating Model for API Platforms
22mAPI and Platform Strategies to Win in Global and Local Markets
23mLessons from Building an API Management Platform
29mAPIs and Event Streaming Dualty