SOA is a form of distributed computing, or more precisely, an architectural approach to establish it. It is maintained on heterogeneous environments by means of API standardization and canonicalization of service activities by service messaging/state messaging. The ability to arrange the service composition dynamically and in an agnostic way is arguably the main benefit of this architectural model, as demonstrated in all the previous chapters. This is where the money is. About 80 percent of all SOA patterns are focused on achieving composition-centric SOA characteristics (among others mentioned in Chapter 1, SOA Ecosystem – Interconnected Principles, Patterns, and Frameworks) directly:
Implementing Service Inventory and maintaining a dependable Service Registry
Minimizing the Service Adapter layer and avoiding transformations
Abstracting services and maintaining their state, even for completely stateless services
Allowing...