Architecture Remediation
summary
Many startups end up with an unmaintainable monolith that slows time to market and lacks CI/CD; remediation starts with refactoring to domain folders, extracting repeated logic, and applying DRY/KISS/YAGNI and SOLID plus dependency inversion so code becomes readable and testable. Architecturally, apply the strangler pattern with an orchestrator to peel services out of the monolith, add BFF layers per client to reduce surface area, and rebuild tests toward a unit-heavy test pyramid so deployments stop breaking.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:33Startup’s monolith problem
- 4:26Signs of legacy code
- 9:04Remediation principles
- 13:21Code design best practices
- 16:54Strangler pattern demo
- 19:22BFF pattern explained
- 20:44Test pyramid strategy
- 22:07Summary and legacy fixes
related talks
59mDecomposition Patterns
59mArchitecture Modernization Anti-Patterns: The Cost of Good Intentions
46mArchitectural Patterns and Approaches Supporting Refactoring(...)
47mDomain Driven Transformation—How to Bring Back Sustainable Architecture to
37mStart with DDD when you have a monolith
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
23mRe-Architecting Big Environments
39mMinimal Viable Architecture