Cloud Native Development Patterns and Best Practices

Single responsibility

The single responsibility principle says that a component should have one and only one responsibility; the entire responsibility should be encapsulated in that component; it should do that one thing and do it well; it should have high cohesion such that everything in the component belongs together; it should have only one reason to change. The trick is determining what that one responsibility should be. The bounded context, component patterns and data life cycle decomposition strategies help us whittle components down, but here I want to focus on only one reason to change part of the principle. Part of the goal of cloud-native systems is to enable teams to rapidly deliver innovation with confidence, in other words, to ...