Alf Kåre Lefdal

45%
Flag icon
It is usually best to try to align software boundaries with the different business domain areas. A monolith is problematic enough from a technical standpoint (particularly, the way it slows down the delivery of value over time as building, testing, and fixing issues takes increasingly more time). If that monolith is also powering multiple business domain areas, it becomes a recipe for disaster, affecting prioritization, flow of work, and user experience.
Team Topologies: Organizing Business and Technology Teams for Fast Flow
Rate this book
Clear rating