Service Oriented Architecture

Learn about SOA

SOA 1

view softwaer as a collection of services

SOA 2

focus on the service provided rather than on the domain data model we use to provide it

difference in DO and SOA (target)

DO targets technologists, SOA targets businesspeople

difference in mindset

RPC and DO emerged from enterprise computing, SOA emerged from business integration

details on emerging from business integration (SOA)

IT support for supply chains and complex operations, facilitating interactions without losing control over valuable data

difference in granularity

DO divides system into objects or clases, typically small, SOA divides the system into services, typically heavier

difference in exposure

DOA is object-oriented, SOA is service or business oriented

difference in initiating further interactions with the customer

DO systems may expose too much, SOA systems can be more closed and therefore control exposure

difference in surface area

SOA system will have a reduced surface area for its interfaces so there are fewer larger entities making calls and fewer dependencies between services

complexity 1

passing data references is harder, the data model is hidden and data doesn’t have an endpoint that can be passed around

complexity 2

needs extended service query interfaces or standardised documents containing all the relevant details

pro of representing everything as documents 1

would allow arbitrarily structured data, the same data in multiple formats

pro of representing everything as documents 2

services become stateless, have less need for concurrency control and can therefore scale better