SOA - An Architect View

SOA [ Service Oriented Architecture ]
"SOA = Loose Coupling"

Trying to pen down my important markings of SOA and how to approach.

1. Architects  mostly uses an existing product(s) to build solution to address an specific problem
2. Said that, mostly uses existing products(s) , at times have to fill in the requirements from BA (business analyst ) and provide an overall high level needs for building newer products - which goes to the product engineering teams
3. Data Layer is the most important of below - always insisted to use standardized data format for communication
4. Technology Layers  SOAP/HTTP with JSON/XML brings values to standardize
5. LOOSE COUPLING of systems and components are key here as i had quoted right above in the first
6. Note : Key SOA solutions are not just ESBs

Read  carefully below diagram two layers of solution design, before that always remember

Technology Layer Break down of components

1. Service Container : where data is translated (if needed) to meaningful relational information an example is to translate multi-system information into standardized representation for services, Adapters are used for this translation of data
2. Broker : is an adapter to ship data from one system to another
3. Process coordinator : processing or warehousing of data and flow are handled here

Costly Mistake

1. Many a times the processing of data like business logic are done by broker instead of service container
2. Also at times broker used in place of process co-ordinator

Loose Coupling

1. Data in one system means different in another system, always represent the data and the meta data for specific system
2. Map domain data to message data
3. Eliminate unnecessary dependencies