Why your company needs an internal API and what you should do about it
summary
Companies build a light service platform of small microservices that expose OpenAPI proxies over legacy ERP/CRM, use Azure API Management (or similar) for auth, rate‑limiting, caching and a developer portal, and generate C# and TypeScript clients from specs. Case studies show about 2x faster MVP/app delivery and big personnel cost savings. Start by adding OpenAPI surfaces for the slices you actually need, resolve master‑data ownership, and evolve via events or direct update patterns rather than rewriting core systems.
AI-written summary · about
chapters (15)
- 0:00The problem with legacy systems
- 1:11Constraints and technical debt
- 2:51The need for speed and innovation
- 4:40The API bridge
- 5:54Adopting a common language
- 8:13Open API specifications
- 10:22Generating the specification
- 13:44Implementing the API layer
- 17:11Incremental development
- 20:51Layered architecture
- 24:33API management tools
- 26:48Azure API management example
- 30:51Unified service surface
- 32:18Master data management
- 36:41Where to start
related talks
49mWhy you need an API, and what to do about it
08mMicrosoft
27mEnterprise API management in agile integration
25mHow API-as-a-Service can Improve CX, Scalability, and Security
26mFrom project to reality let's explore some API
29mImpact of Microservices Architecture on API Management
29mAdapting to an API Enabled World (Panel Debate)
29mStrategies versus plans for financial services APIs