SOA Patterns > Service Implementation Patterns > Service Façade
Service Façade (Erl)
How can a service accommodate changes to its contract or implementation while allowing the core service logic to evolve independently?
Problem
The coupling of the core service logic to contracts and implementation resources can inhibit its evolution and negatively impact service consumers.
Solution
A service façade component is used to abstract a part of the service architecture with negative coupling potential.
Application
A separate façade component is incorporated into the service design.
Impacts
The addition of the façade component introduces design effort and performance overhead.
Principles
Architecture
Service
Facade logic is placed in between the contract and the core service logic. This allows the core service logic to remain decoupled from the contract.
Related Patterns in This Catalog
Agnostic Sub-Controller, Concurrent Contracts, Contract Denormalization, Data Format Transformation, Decoupled Contract, Distributed Capability, Inventory Endpoint, Partial Validation, Proxy Capability, Service Decomposition, Service Refactoring
Related Patterns in Other Catalogs
Related Service-Oriented Computing Goals
Increased Vendor Diversification Options, Reduced IT Burden
Related Publications
SOA Pattern of the Week: Service Façade (InformIT)
This pattern is covered in SOACP Module 7: Advanced SOA Design & Architecture with Services & Microservices.
For more information regarding the SOA Certified Pofessional (SOACP) curriculum,
visit www.arcitura.com/soa.
This page contains excerpts from:
SOA Design Patterns by Thomas Erl
(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)
For more information about this book, visit www.arcitura.com/books.