Web services have changed the landscape of how we program internet applications. The rise of XML and HTTP, and with it a raft of specifications built on SOAP, has led to a new
generation of distributed applications.
Finding your way in this new world can be tricky, however, with much noise being made by vendors and standards groups alike. If you actually want to use web services in your
application, how do you know what technologies to trust? Learning the acronyms is often tricky enough. SOAP, SOA, REST, WSDL: and they're just the easy ones!
This collection of articles from XML.com's Web Services site is here to help you navigate through designing web services implementations. Written by regular XML.com columnist
Will Provost and Thomson Corporation's Dr. Hao He, these articles will help orient you as to what web services actually are and how to design them. You will benefit from the experience of practioners deploying web services in the real world, and be shown where pitfalls lie.
The content is pretty sparse, focusing on the 'big picture' behind web services, rathern than actual code and implementation. That said, there are some code, XML, and UML examples. It runs for roughly 34 pages and covers:
SOA - (Service Oriented Architecture) XSLT - Using them to integrate various data models Interoperability WSDL - RPC-style web services
It misses the train somewhat, as RESTful services became the dominant web services standard. In the SOA section, RESTful services are covered.
The XSLT section is somewhat interesting, as it uses the Adapter design pattern to connect mismatched data models.
The interoperability section uses UML format to describe web services. I didn't find it particularly useful, other than adding to my admittedly sparse UML vocabulary.
The last section talks about WSDL services. I did not find it useful.
Bottom Line No, I would not recommend this to a friend