Object-Oriented Lessons for a Service-Oriented World
summary
Argues that the useful claim is to apply OO principles (SOLID, SRP, DRY, dependency inversion, Law of Demeter) to service boundaries so services behave like services as objects and APIs carry behavior as APIs as messages not just data. Demonstrates using hypermedia (HAL JSON, link relations, GitHub examples) and warns serialization cost and network latency so cache control and ETags must be first-class, and shows how hypermedia-driven clients avoid brittle versioning.
AI-written summary · about
chapters (12)
- 0:00Start
- 7:15NETWORK-BASED APPLICATION SOFTWARE
- 9:40YOUR APPLICATION SPECIAL SNOWFLAKE
- 10:34DEPENDENCIES
- 11:16OBJECT ORIENTED DESIGN
- 16:36LAW OF DEMETER MORE LIKE GUIDELINES OF DEMETER
- 17:11DEPENDENCY INJECTION
- 18:13Cache is King
- 21:01NOUNS VERBS
- 21:51GET POST PUT DELETE
- 22:31WHAT ABOUT HYPERMEDIA?
- 23:18THIS IS NOT YOUR Rails' REST
related talks
40mWe are not Object Oriented anymore
57mSOA lessons learnt (OR Microservices done better)
28mSOA and APIs : Fearless Lessons From The Field
54mServices, Services, Everywhere!
01h 00mService Oriented Architecture for Robust & Scalable Systems
48mService Oriented Architecture - Slice and Dice
52mSOA lessons learnt OR Microservices done better
30mService Oriented Design in Practice