Uh-oh, it looks like your Internet Explorer is out of date.

For a better shopping experience, please upgrade now.

Understanding SOA with Web Services (Independent Technology Guides Series) / Edition 1

Understanding SOA with Web Services (Independent Technology Guides Series) / Edition 1

4.0 1
by Eric Newcomer, Greg Lomow, Greg A. Lomow, David Chappell

ISBN-10: 0321180860

ISBN-13: 9780321180865

Pub. Date: 12/28/2004

Publisher: Addison-Wesley

Praise for Understanding SOA with Web Services

"This book does the best job of describing not only "where we are" in the timeline of enterprise integration efforts, but also providing strategic guidance for where we need to be. The authors have worked diligently to break down the integration problem into functional areas, and send

Customer Reviews

Average Review:

Post to your social network


Most Helpful Customer Reviews

See all customer reviews

Understanding SOA with Web Services (Independent Technology Guides Series) 4 out of 5 based on 0 ratings. 1 reviews.
Guest More than 1 year ago
Reading this book left me overwhelmed with the acronymic promiscuity resplendent in this field. The authors describe SOA in conjunction with XML, Web Services and a whole slew of Web Services subsets, like WS-Transactions, WS-Trust, WSDL and WS-BPEL. At some point, this jargon acts as a conceptual barrier to newcomers. The book strives to overcome this, and does a creditable job. But it still can be confusing. Perhaps the key note is how the book's subject differs from other topics, like Web Services or BPM. Much detail is given about this. There is one simplifying point. Do you come from a Java or C# background? If so, then you are familiar with interfaces. And how if you are coding a large project, good practice is to have major classes implement interfaces. So that one class does not call another directly, but instead uses an instantiation of an interface. This leads to a more modular and robust design. By analogy, this carries over well into SOA, in the context of Web Services. Of course, you should be aware of the limitations of pushing the analogy too far. As the book shows, SOA is for distributed systems. Which is more complicated that running one Java program on one computer. Still, you can migrate a design attitude. But once you realise the analogy, a lot of the book's complexity can be pushed to a lower level of detail.