SOA and APIs : Fearless Lessons From The Field
summary
Three field lessons: pick models and tools that fit how much of the stack is controlled (REST suits loosely controlled, distributed systems; SOAP exposes components; CRUD models objects), cultivate broad experience across those styles, and apply the USE Paradigm — usability, scalability, evolvability. Several clients adopt hypermedia message-driven APIs (about half a dozen customers actively prototyping it), one commerce client ships workflow instructions to chips so devices change without app updates, Etsy-style multiple daily releases prove measure-and-iterate, and engineers are urged to scale early.
AI-written summary · about
chapters (7)
- 0:00Start
- 16:59Heading toward Hypermedia
- 20:57Iterate
- 22:17Automate
- 22:29Evolvability is defined as the capacity of a system for adaptive change.
- 24:17Versions 'break , extensions don't
- 24:41Agility
related talks
57mSOA lessons learnt (OR Microservices done better)
27mBuilding Great Web APIs
24mDesigning the APIs for an Internal Set of Services
01h 00mService Oriented Architecture for Robust & Scalable Systems
35mObject-Oriented Lessons for a Service-Oriented World
27mThe API Design Strategy You Need for Growth
23mLeverage APIs to Transform Your Business Landscape
21mScaling API Design