REST, SOAP, Hypermedia: When, why & how to use what
summary
Public APIs skew heavily toward REST while finance and B2B still use SOAP because the WS- stack supplies WS-Security, X.509 signing and encryption, WS-ReliableMessaging* and non‑HTTP transports. A working example is Essent: an internal SOAP ESB plus an API layer that translates to REST/JSON for mobile, keeps SOAP with WS-Security for partners, and uses SAML for employees. Result: real‑time smart‑meter and EV‑charger endpoints publicly available, third‑party mashups created, and legacy systems remain stable while mobile apps deploy faster.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:40SOAP vs REST
- 2:20Martin Lawrence
- 3:00When to use SOAP
- 3:40Transport level security
- 4:55Delivery assurance
- 5:40Other reasons
- 7:25Hypermedia
- 8:35Catalog API
- 9:05Graph API
- 9:30Extensibility
- 10:00Disadvantages
- 10:50Resources
- 11:40Mark ONeil
- 12:15RWE
- 12:40Why
- 14:25What
- 17:00Benefits
- 17:35Conclusion
related talks
28mSOA and APIs : Fearless Lessons From The Field
30m2004-2024 : Two Decades of Web Services, A Retrospective
31mAPI testing journey through web protocols
42mREST API design good practices
01h 01mAn Architect's Approach to API Strategies
01h 39mLet’s have some Effective REST
42mLet’s Have Some Effective REST!
53mEffective Design of RESTful APIs