Please log in to watch this conference skillscast.
Not taking into account what a piece of software represents in real life can lead to higher complexity, additional development costs, difficult refactorings, and ultimately, a software that no longer scales. If it gets far enough out of hand, at some point, new features cannot be implemented if they’re not compatible with the current architecture, because they would be too expensive to implement. In this session, we’ll look at some real-life examples and at some of the things to keep in mind in order to avoid the above-mentioned issues.
YOU MAY ALSO LIKE:
- Functional Domain Models in Practice with Marco Heimeshoff (Online Workshop on 17th - 21st October 2022)
- Domain Driven Design & Legacy Systems with Marijn Huizendveld (In-Person) (in London on 22nd - 24th November 2022)
- Software Architecture in a DevOps World (SkillsCast recorded in February 2022)
- Understanding Microservices: A Guide for the Monolithic Developer (SkillsCast recorded in October 2021)