Ajith Kallambella said
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
(...)
P. Leadbetter said
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
Paul Lopez said
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.
Anonymous said
I bought this book with lot of hopes, all I got is a JUNK. This book is nothing but a copy of specs obtained from OACIS and W3C. If you think about on implementing a WORKING Web services architecture using Java or .NET, then all you find is ZERO content. There is no working real-world architecture or implementation example discussed in this book. All the chapters are disconnected.
Waste of money.
said
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!
Comments