SOD Microservices - Daniel Jones, EngineerBetter

on YouTube ↗40m

" summary

Argues microservices are a deployment concern and recommends a monolith-first Service-Oriented Design that’s easy to split later, with practical steps for Java/Spring apps: separate gateway-orchestration-domain-data layers, enforce CQRS (reads side-effect free), use immutable parameter objects, adopt event-driven calls and event sourcing, handle idempotency and deterministic IDs, and reconcile divergent histories with vector clocks so eventual consistency can be detected and remediated.

AI-written summary · about

" chapters (14)

1. 0:00Introduction to microservices
2. 1:04SOA principles for microservices
3. 3:50Why service buses declined
4. 5:17Eventual consistency basics
5. 6:01Future-proofing monoliths
6. 9:09Four service layers explained
7. 13:00CQRS for clarity
8. 14:26Preparing for events
9. 18:17Idempotency and determinism
10. 24:38Event-driven architecture
11. 25:22Event sourcing benefits
12. 27:30Handling conflicts with vector clocks
13. 35:23Key takeaways summary
14. 36:33Q&A on event communication

" related talks

• 57mSOA lessons learnt (OR Microservices done better)Sean Farmar · Build Stuff 2017
• 52mBuilding monolith applications that could scale to microservices..David Gomez G. · Devoxx Ukraine 2021
• 50mEmbracing MicroservicesGrzegorz Piwowarek · Build Stuff 2024
• 52mSOA lessons learnt OR Microservices done betterSean Farmar · Voxxed Days Vienna 2017
• 48mIT Architecture : All your micro-services are wrong PERIOD!Dwight Matthys · Voxxed Days Brussels 2023
• 49mDDD & Microservices: At Last, Some Boundaries!Eric Evans · GOTO Berlin 2015
• 38mMicroservices, a bittersweet symphonySebastian Sogamoso · RailsConf 2015
• 24mPatterns of Evolution from Monolith to MicroservicesKarina Mora · HashiTalks 2022