How to position the API driven Architecture
summary
Company history shows SOAP services since 2003 evolving into REST JSON APIs and the lesson is treat APIs as a program not a project. The concrete checklist is six items: API product owner, centralized API development team, API roadmap, API architecture, API standards and guidelines and API data governance (JSON is “data as new oil”). Expect recommendations to use vendors like awso2 and musesoft for gateways, adopt layered APIs (experience/process/system) and prioritize reusable APIs under central ownership.
AI-written summary · about
chapters (13)
- 0:00Start
- 7:27Headless Technology
- 8:07Ambient Computing will demand a different level of thinking
- 9:14What's driving Digital Transformation
- 10:33API Centric Architecture
- 11:23API Gateway
- 12:44How to Position an API Driven Architecture
- 13:19API Product Owner
- 14:47API Development Team
- 16:28API Roadmap
- 18:07API Architecture
- 20:18API Standard & Guideline
- 22:08API & Data Governance
related talks
26mRevolutionizing Business with API-First Strategy: Key Insights
30mDelivering API First: Is Your API a First Class Citizen?
38mHow APIs Change Software Development
23mLeverage APIs to Transform Your Business Landscape
01h 01mAn Architect's Approach to API Strategies
26mAPIs are the new skin of your organisation
45mSecurity Architecture, An Adventure?
18mStrategically planning your API ecosystem model