SOA Patterns > Foundational Inventory Patterns > Service Normalization
Service Normalization (Erl)
How can a service inventory avoid redundant service logic?
When delivering services as part of a service inventory, there is a constant risk that services will be created with overlapping functional boundaries, making it difficult to enable wide-spread reuse.
The service inventory needs to be designed with an emphasis on service boundary alignment.
Functional service boundaries are modeled as part of a formal analysis process and persist throughout inventory design and governance.
Ensuring that service boundaries are and remain well-aligned introduces extra up-front analysis and on-going governance effort.
Related Patterns in This Catalog
Capability Composition, Contract Centralization, Contract Denormalization, Domain Inventory, Enterprise Inventory, Entity Abstraction, Inventory Endpoint, Logic Centralization, Metadata Centralization, Policy Centralization, Process Abstraction, Proxy Capability, Schema Centralization, Service Decomposition, Service Refactoring, Utility Abstraction
Related Service-Oriented Computing Goals
Increased Federation, Increased ROI, Reduced IT Burden