Summary - 4 major parts
- - Part 1 general SOA
- - Part 2 SOA details and components – Arch etc
- - Part 3 SOA other important bits – governance, security
- - Part 4 Where you can apply SOA, litmus test and how to apply
- - Part 5 real life SOA, how biggies are using it.
Chapter 1
- Nothing special
- Why SOA is needed? Whats it in there?
- SOA is nothing but reusing existing architectures and processes, and integrating with other architectures and processes to conduct business smoothly, in this dynamic and ever changing market place.
- This integration is independent and abstract from layers, i.e. business layer shouldn’t worry about technology layer and vice versa
Chapter 2
- More about SOA how the SOA architecture evolves. How business layer and technology layer differ in terms of design, implementation, people and still achieving the results.
- SOA is about
o Only Business applications not all applications can be developed using this
o Black box components, abstracting unnecessary complexity under the hood
o Loosely coupled components, less dependency in terms of interaction among the components
o Achieving results thru well defined services using black box components
- Legacy systems/code can be used with SOA Components by providing “adaptor” which forms bridge between Legacy and SOA component
- SOA supervisor monitors all components are behaving as desired and make a corrective action if required.
- Conclusion of the chapter
o SOA enables separation of Business /functionality from Legacy System connections
o In other words, your architecture diagram can have clear separation of Business layer and plumbing layer / technology layer which connect to legacy code. SOA enables layer separation and evolution both layers i.e. business and technology independently. Evolution is the need of current market place as technology and business are changing so rapidly.
