API First to the Extreme - Federated API Design via Inner Sourcing
summary
ADP moves from a centralized API design bottleneck to a federated inner‑sourcing model where domain teams submit OpenAPI/Swagger specs via Git pull requests, reuse a living library of 700 reusable JSON components, and emit events on every data write. A packaged, flattened API registry makes specs machine‑readable for code generation, proxies, monitoring and a marketplace. Custom OpenAPI/Swagger extensions add UML and sequence diagrams. Production rate of APIs rises after federation.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:39Today's Agenda
- 1:26The Adp Api Journey before Working for Enterprise Architecture
- 9:18What Makes an Api Canonical
- 13:35Inner Sourcing
- 16:52Template
- 20:55Apa Registry
related talks
22mFederated API Management - The next iterations
23mFederated API Management - The next iterations
24mAPI design is where culture and tech meet each other
26mFostering API Productization in Federated API Architecture
39mAPI Development in 2017
30mAPI Code First vs Design First
21mAPI Discovery done right: Engaging the right people with your APIs.
21mMastering API Design: Why Community Matters