|Service-Oriented Architecture (SOA): Concepts, Technology, and Design|
What I intend to do here is pick up the key thoughts, and concepts which I encounter while reading the above book. This one of a couple of SOA books I’m reading currently.
I’m not coming into this discussion of SOA without any previous experience of the topic. So, hopefully the will be more than a 101 level discussion of the concepts.
The “A” in SOA is important to understand. Architecture here is driving at a vendor, and technology, agnostic concept. This concept of the “service orientation” of the components which are integrated into an implementation. The service components “publish” a definition of the service they provide through the service contract (the semantic meaning of what the service does is something which a WSDL contract does not contain – we need to look to other standards and development to see this materialise). The services communicate through messages (which should be self contained and governing objects).
Web Services are the current way that these aims are currently achieved. In is important to understand that “just using web services” does not make a system SOA. Web services are just a technology platform which allows the implementation of SOA.