Smash the Monolith: Refactoring into SOAs
summary
Shows how a monolithic Ruby application was refactored into service-oriented architectures (SOAs). Covers the problems encountered during the refactor and the concrete steps, tools, and patterns used to break the monolith into services.
AI-written summary · about
chapters (32)
- 0:00Intro
- 0:45Agile Development
- 2:16Degraded Design
- 5:01Legacy Applications
- 6:59Code Archaeology
- 9:51Big Upfront Design
- 10:14milestones
- 10:32evolution
- 10:45predictability
- 10:58velocity
- 11:13Ad-Hoc Architecture
- 11:31layers
- 11:41extra verbs
- 11:59god classes
- 12:30complex relations
- 12:41junk drawers
- 12:55gem explosion
- 14:03execute
- 14:35Hexagonal Architecture
- 16:52messages objects
- 18:05substitution
- 18:21Attacking the Monolith
- 19:03object promiscuity
- 19:45behavior modules
- 20:39meta applications
- 21:02persistence as a Service
- 22:01Small App Ecosystems
- 23:41understandable
- 24:00add versatility
- 24:11replaceable
- 24:23Interchangeability
- 26:58Achievement Unlocked
related talks
35mFrom Monolith to Services: Lessons Learned
40mFacing the Monolith Overcoming Monolithic Applications with SOA
34mSOA and the Monolithic Rails App Anti-Pattern
01h 00mService Oriented Architecture for Robust & Scalable Systems
01h 03mFrom Monolith to Microservices: Story and Practice
59mDecomposition Patterns
23mAbstracting a Service - A Case Study in Forward Thinking with SOA
01h 52mMasterclass: Let's Cut the Monolith