Web Services and Service-Oriented Architectures: The Savvy...

Features

• Cover Type: Paperback with 245 pages
• Published by: Morgan Kaufmann
• Edition: 1st Edition April 1, 2003
• Written in: English
• ISBN 10 Number: 1558609067
• ISBN 13 Number: 978-1558609068
• Book Dimensions: 8.8 x 6 x 0.5 inches
• Weighs: 12.6 ounces

Product Review
"The discussion on the common beliefs about enterprise architectures and how they relate to Web services is a gem and worth the price of the book. Similarly insightful chapters cover the impact of Web services on the enterprise, adoption steps and change management issues in implementing Web services projects. This a great book that every manager contemplating a Web services project should read." - Toufic Boubez, Ph.D., Author of "Building Web Services with Java: Making Sense of XML, SOAP, WSDL and UDDI" -- Review

Product Review
"The discussion on the common beliefs about enterprise architectures and how they relate to Web services is a gem and worth the price of the book. Similarly insightful chapters cover the impact of Web services on the enterprise, adoption steps and change management issues in implementing Web services projects. This a great book that every manager contemplating a Web services project should read." - Toufic Boubez, Ph.D., Author of "Building Web Services with Java: Making Sense of XML, SOAP, WSDL and UDDI"

Reader Reviews
This is management style book. It talks about all of the good things about web services. Yet it makes several crucial mistakes that clearly show that the author is by no means aware of what a service oriented architecture must provide. The crucial points that lead to failures using distributed architectures in the grand scale are not discussed. The whole problem is seen totally as a management issue. It is not. It is a vital technical challenge, and web services are by no means ready to take that challenge. Problems like transactions, security, undoability, Quality of service etc are not even slightly solved today. The savvy managers should read the book, give it to a savvy software architect, and afterwards discuss very carefully. Another annoying feature is that the author sees technical people as the ones being the greatest opposition to service oriented architectures. They can be, but the real problem are business managers and departments who do not want to be service providers in the first place because it means giving up some of their power and probably loose some of their workforce.