Multi-form API Management
summary
Argues that events, messages and REST/GraphQL endpoints must be managed the same way as APIs and shows working choices: use AsyncAPI for Kafka to document event streams, OpenAPI for REST, and API Connect/App Connect plus MQ for integration; one bank turned internal services into partner-facing APIs and launched a new business model in three to four months; recommends portals for discoverability, enforcement via security boundaries (enterprise gateway vs lightweight proxies), and tooling to lint/scan APIs for consistent policies.
AI-written summary · about
chapters (10)
- 0:00Welcome
- 5:59Defining multi-form API management
- 8:29Why multi-form APIs matter
- 13:05IBM’s multi-form APIs
- 17:35Making APIs accessible
- 21:10Addressing audience questions on APIs
- 22:15API trends in India
- 24:25Standards in API development
- 26:28Securing multi-form APIs
- 30:18Security boundaries
related talks
01h 01mWorkshop: 5 Key API Management Success Strategies You Need Today
23mEvent API Products: Maximizing the Value of Your Event-Driven Architecture.
15mEvolution of API Management and Emerging Trends
27mEnterprise API management in agile integration
26mAPI Management, meet Event Management
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise
23mContinuous API Strategy Management
29mAsyncAPI and Event API Products; a Match Made in Heaven