This line was removed.
This word was removed. This word was added.
This line was added.
Changes (1)View Page History
h3. So what should we have been doing?
To be direct and precise, we should have realized that we need to understand the concept of a service. If we explore the successful work in [building services the last 15+ years], we will end up with something like the [Service Manifest]. In short, the service manifest defines the responsibility of a service, where the most important stuff is the _single responsibility principle_, mainly to ensure that our *services are good building-blocks* for our solution.
Taking this reflection a bit further, we quickly realize that we need some way of categorizing/grouping your services from a non-functional dimension. A great example of such categorization can be found in [Service categorization]. If we do a good job at categorizing our services, we will be able to add requirements and rules for the different categories of services, as you can see in this [Design-Time Governance] example.