Removing the legacy, the microservice approach
summary
Discusses using microservices to manage and refactor large PHP legacy applications, evaluating reasons for and against applying a microservice architecture. Explains common failure modes of refactoring without microservices, how projects typically start to go wrong, and gives practical guidance on getting started with a microservice-based approach to rebuild or improve highly coupled legacy systems.
AI-written summary · about
chapters (16)
- 0:00Legacy system challenges
- 1:11Legacy systems unmanageable
- 3:00Perfect designs illusion
- 5:10Monolith to microservices
- 7:52Managers and legacy systems
- 10:02Microservices performance limits
- 12:10Fresh start vs refactoring
- 14:39Testing legacy vs microservices
- 17:33Legacy system breakdown
- 20:02Microservice testing strategies
- 22:51Migrating legacy to microservices
- 25:40Microservice monitoring debugging
- 27:31Small focused services
- 29:57Cultural shifts for microservices
- 31:45Microservices starting tips
- 34:14Summary
related talks
36mJava: Microservices...decisions, decisions, decisions everywhere
46mArchitectural Patterns and Approaches Supporting Refactoring(...)
34mMigrating a High‑Load Project to Microservices
46mFrom microservices to migroservices
32mMicroservices: A retrospective
51mResponsible Microservices
43mGo micro with Microservices
52mHow to work with legacy so neither you nor the project burns out