...
- Service Design Methodology favors separation along service boundaries. Services define such boundaries as interfaces and as such provide a natural breakdown that can be developed in smaller chunks. This limits the scope and impact of refactoring.
- As technological choices such as application frameworks, ORMs, rules engines, identity management, etc. changes through the course of a project, changes can be prioritized and implemented on a service by service basis. Change gets a lot less scary when an entire project doesn't need to be redone all at once.
- If the impacted service providers are determined on a feature by feature basis, these boundaries can be used as collision avoidance ina distributed in a distributed development environment.
Agile OSIDs
...