A Guide to Managing External APIs in Enterprise Systems
summary
Converts a callback-heavy comms API into a constrained C++ wrapper that returns future/promise and carries responses as move-only results (unique_ptr) to avoid accidental copies, integrates with a coroutine-based executor supporting ~50,000 coroutines in flight, and uses Google Mock for unit tests. Builds a single service proxy that routes between old and new backends, limits branching to a few files instead of hundreds of handlers, enables phased migration over years, and proves decommissioning and rollback are simple and safe.
AI-written summary · about
chapters (8)
- 0:00Introduction to managing external APIs
- 7:08Understanding enterprise API usage
- 17:43Testing strategies for API wrappers
- 21:59Handling API changes in production
- 31:53Building a service proxy for migration
- 41:08Production deployment and decommissioning
- 46:28Recap and key takeaways
- 49:18Q&A and closing remarks
related talks
01h 00mManaging External API’s in Enterprise Systems
37mAvoiding the dogma - a plea for mutable objects
01h 02mRetiring the Singleton Pattern: Concrete Suggestions for What to use Instead
37mAPI Horror Stories from an Unnamed Coworking Company
58mA Practical Guide to Loose Coupling
23mLeverage APIs to Transform Your Business Landscape
33mEverything is an API
24mAPI as the powerful EA lighthouse for a Composable Information System.