Federated API Management - The next iterations
summary
Presents a five-step federated framework that moves federation from multi-gateway marketing to concrete runtime coordination: teams own API contracts and policy-as-code (OPA Rego) expresses policy intent in Git, the platform enforces execution, and gateways query OPA at runtime. Shows a working example rule (only internal services may call API), calls out X-extensions as nonportable metadata, and lists anti-patterns (platform owning policy, spec-only enforcement). Claims federation succeeds when there is team ownership plus portable, auditable policy decisions.
AI-written summary · about
chapters (13)
- 0:00Federated API management intro
- 1:31API federation origins
- 3:38Federated framework steps
- 5:48API behavior contracts gap
- 7:55Distributed ownership in API management
- 9:21Team topologies for governance
- 11:31Policy ownership and runtime behavior
- 14:43Need for open policy spec
- 16:11Open Policy Agent enforcement
- 18:40Policy as code in federated systems
- 20:06Runtime coordination and trust
- 20:46Anti-patterns in API management
- 21:51Key takeaways
related talks
23mFederated API Management - The next iterations
26mFostering API Productization in Federated API Architecture
28mAPI First to the Extreme - Federated API Design via Inner Sourcing
25mEstablishing a Specification Framework for API Management Federation
10mFrom Fragmentation to Federation: The Future of API Management.
27mEnterprise API management in agile integration
25mFostering API Productization in Federated API Architecture
40mAutomated Governance in Practice