Rating: 
Summary: An excellent overview
Review: A great guide to designing and implementing web services and the common challenges and pitfalls that can be found along the way.Examples, patterns and case study provide excellent illustration while the subject matter is delivered in a consistent and surprisingly easy to read manner. I'd recommend this book to anyone that wants to find out the ins and outs of providing web-services, rather than developing a simple web service for their own benefit - most .NET books can deal with that in a couple of pages. Buy this book to dig deeper and find out about the issues that you should be considering. Enjoy
Rating:
Summary: More stuff less chaff !!
Review: Consider this - Web Services and SOAP is perhaps the only recallable evolution of technology that has witnessed the single largest involvement of standards bodies and industry bellwethers. The result? A puzzling plethora of proffered protocols that continues to confuse both sideliners and early adopters every day.
While managers are finding it increasingly difficult to understand the direction, developers are craving for clarity, consistency and a unified approach for WS adoption. "Give me the tools" they cry every day, while they keep adding to their "To Read" list a handful of new acronyms every week. The big question is, when can we build Rome, if at all?
With a gentle and brief (thank god!) introduction to underlying concepts such as SOAP, XML and UDDI, authors start talking about broader concerns - conversation, transaction, security, workflow, QoS and everything in between. While accentuating nuances of evolving standards and guessing the future trends, authors offer strategies, patterns, and tips on pitfalls to avoid. They skirt around the political interoperability issues around J2EE and .NET and focus purely on the standards. Architect's Note included at the end of every chapter makes title justified.
An implementation of WS-based ordering system presented as a case study concludes the book by bringing it all together through excellent step-by-step approach.
Although almost a year old, this book can be a survival guide for people in the trenches and the ROI-Savvy managers as well. It helps you tell the wheat from the chaff.
Ajith Kallambella
(...)
Rating:
Summary: Solid book. A single book that covers all the bases.
Review: I just got this book. This book is different from other Web Service books that go on and on about one or two topics. Instead, this book looks at developing enterprise applications using Web Services and addresses all of the issues that enterprise architects and developers face. The writing is informal and easy to understand. Some of the chapters are a little longer than is needed. But, definately a solid resource. A "one stop shop" for Web Services and enterprise software. Cheers.
Rating: 
Summary: Nice Vendor-Neutral Description
Review: Interested in designing a Web Service? But you have never done so? Well, texts have started to appear; the latest being this one by Chatterjee and Webber. It has several merits. Perhaps the strongest is that it does not take sides in the J2EE versus Microsoft's .NET debate. Wait a minute, you might say! You have heard enough about Web Services to know that it is vendor and platform independent, much like HTML, which is an industry standard. So how could a book on Web Services NOT be neutral? Well, consider how HTML is a standard, but different browsers render an HTML page slightly differently. And HTML is pretty simple, remember. Now consider that Web Services is far more complex. The XML messages going to and from a WS are vendor neural. But, as is made clear by the examples in the book, the XML does not describe the processing logic implementation on a WS provider, by deliberate design, to make things loosely coupled. But if that provider has, say, a transaction capability, then you can get into the nuances of implementation. Thus, if for example you get a book on J2EE WS, that may be fine. But it may also be hard to disentangle the truly neutral design details from the necessarily hairy implementation. The neutrality of this book should be a design virtue to you. Look, if you are going to build a WS, you probably already have preferences for .NET or J2EE (or something else). So, indeed, do get a WS book specific to that platform. But consider this book as a good second opinion, and much cheaper than hiring a consultant.
Rating:
Summary: Best coverage on the topic
Review: Over the past year, I have read quite a few books on Web Services, some good, others not so good... but this book really stands out.
The concepts were covered in sufficient details and in a very informal manner. It gives you a very good idea what you would need to consider when deciding to implement a SOA solution in your organization.
Highly Recommended!
Rating: 
Summary: Save your money
Review: This book isn't much better than freely available online documents on the same subjects. The book suffers from the usual problems of a book with too much level content and no practical hands-on information -- Architecture with out practical solution or a prototype model is constructing a building with out foundation. The authors explained individual topics to the extent that it is even confusing. I found this is the last book to be used for quick reference. This book is quite useless to me and I am a googling around for better information.
Rating:
Summary: The most comprehensive book on enterprise web services
Review: This book presents the most recent snapshot of development in web services area. It covers not only the fundamental constructs of the technology in detail but also the advanced topics that arise in any enterprise-level projects. The authors show how web services address such common problems as transactions and security without mystifying the technology. The best part is the exemplary real-world applications introduced later in the book as a proof that web service technology is a full-fledged distributed computing beyond simple stock-quotes. I would recommend this book to anybody who would like to understand what the technology really is and what it is not, and who considers it for a new paradigm of distributed computing.
Rating:
Summary: The most comprehensive book on enterprise web services
Review: This book presents the most recent snapshot of development in web services area. It covers not only the fundamental constructs of the technology in detail but also the advanced topics that arise in any enterprise-level projects. The authors show how web services address such common problems as transactions and security without mystifying the technology. The best part is the exemplary real-world applications introduced later in the book as a proof that web service technology is a full-fledged distributed computing beyond simple stock-quotes. I would recommend this book to anybody who would like to understand what the technology really is and what it is not, and who considers it for a new paradigm of distributed computing.
Rating:
Summary: A book touches many basic and advanced topics in webservice
Review: This is a book providing up to date information about webservice. It covers almost all the areas in developing enterprise webservice application. For architects/managers, it is detail enough have a overview about webservice architecture. For developers, besides webservice architecture information, it provides some solid samples on webservice development. Although most of the samples are Java/J2EE based, for .NET developers, it is still quite helpful and definitely you can apply to the similar technology in .NET. The text is quite consise and easy to understand. Compared to other books which just talks about one of two topics and then provides many vocabulary, there is no doubt that I'll recommend this book.
Rating:
Summary: good advanced text
Review: This is a good book that starts where most other texts on Web Services stop. If you're really looking to see what's coming over the horizon, how you should be planning for it now, then I'd recommend this book. The text is clear and concise and importantly it doesn't assume everything is Java/J2EE or .NET based. It's fairly obvious that the authors know their subject well and want to let the reader know too!
| 
