Why you need an API, and what to do about it
summary
Argues for a company service platform that sits above messy ERP/CRM/e‑commerce systems, exposing HTTP APIs so teams can innovate without touching core systems; demonstrates using OpenAPI descriptions, generated clients (NSwag, Swagger UI), no‑code connectors (Logic Apps, PowerApps) and Azure API Management as a unified edge. Claims measurable wins from case studies — 50% faster project delivery and 2x faster development — and shows patterns (anti‑corruption proxies, event or push updates, caching, rate limits) to make it work.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:50Backend services
- 3:40Example
- 6:05Business Problem
- 9:51API Definition Language
- 12:30Generating Clients
- 18:20Open APIs
- 27:55API management
- 30:10Azure API Management
- 32:54API Manage
- 34:36Unified view
- 35:55Open API
- 37:12Unified Business API
- 38:43Master Data Management
- 43:30Where do you start
- 46:11Wrap up
related talks
41mWhy your company needs an internal API and what you should do about it
26mFrom project to reality let's explore some API
27mEnterprise API management in agile integration
01h 01mESB, iPaaS, API Management, Microservices...
18mWinning in the API economy
21mPragmatic Strategies for Global API Integration
29mAdapting to an API Enabled World (Panel Debate)
15mEvolution of API Management and Emerging Trends