Architectural Patterns and Approaches Supporting Refactoring(...)
summary
Explains why starting new projects as microservices is usually a bad idea and argues for beginning with a well-structured monolith instead. Describes architectural approaches and best practices—planning, structuring, and refactoring techniques—that prepare a new or existing system for an eventual migration to microservices.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 10:50Smok Fight Club domain
- 21:24Module communication
- 31:32Business processes and sagas
- 40:07Structured monolith pros and cons
- 45:00Summary and Q&A
related talks
59mDecomposition Patterns
01h 03mFrom Monolith to Microservices: Story and Practice
36mRemoving the legacy, the microservice approach
01mModularization: Foundation of Microservices and Monoliths
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
43mMonolith? Microservices? Who cares?
23mArchitecture Remediation
54mMicroservice architecture: approaches and technologies
