Shelby Rizzuto

14%
Flag icon
Thankfully, in practice, this means that we can follow proven software-architecture good practices: Loose coupling—components do not hold strong dependencies on other components High cohesion—components have clearly bounded responsibilities, and their internal elements are strongly related Clear and appropriate version compatibility Clear and appropriate cross-team testing
Team Topologies: Organizing Business and Technology Teams for Fast Flow
Rate this book
Clear rating