This glossary supports the following titles:
SOA Design Patterns
Web Service Contract Design & Versioning for SOA
SOA Principles of Service Design
Service-Oriented Architecture: Concepts, Technology, and Design
Modern SOA Infrastructure: Technology, Design, and Governance
SOA with REST
Next Generation SOA: A Real-World Guide to Modern Service-Oriented Computing
SOA with .NET & Azure
SOA with Java
SOA Governance
SOA Security: Practices, Patterns, and Technologies for Securing Services
SOA and Cloud Computing: Practices, Patterns, Technologies
This glossary also supports the SOA Certified Professional (SOACP) program.
For more information, visit: www.soacp.com
and
www.soaschool.com
|
|
|
utility service
|
A utility service is intentionally based on a non-business-centric functional context. It typically encapsulates common, cross-cutting functionality that is useful to many service compositions, but which is not related to or derived from existing business models.
As a result, utility services are commonly agnostic and reusable. Unlike task and entity services, the involvement of business analysts or business subject matter experts is generally not required when modeling utility service candidates.
Examples of functional contexts that could form the basis of utility services include notification, event logging, exception handling, and currency conversion.
Utility services are also known as: application services, infrastructure services, technology services
See also:
- entity service
- service
- service layers
- service model
- task service
|
|
