August 2018
Beginner
594 pages
22h 33m
English
Content preview from Software Architect's Handbook
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
Start your free trial
Service abstraction
Service contracts should only contain information that it is necessary to reveal, and service implementations should also hide their details. Any information that is not essential to effectively use the service can be abstracted out.
Design decisions, such as the technology used for a service, can be abstracted away. This follows the information hiding principle that was covered in Chapter 6, Software Development Principles and Practices. If a design decision needs to be changed later, the goal is that it can be made with minimal impact.