Appearance
Web Services and Service-Oriented Architectures: The Savvy Manager's Guide (The Savvy Manager's Guides)
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.
Web Services and Service-Oriented Architectures: The Savvy Manager's Guide (The Savvy Manager's Guides)
There must be hundreds of books on Web services, most of them with chapters that read like alphabet soup (UDDI, SOAP, WSDL, etc.). I've read quite a few of these books and it's awfully easy to get lost in the details. Douglas Barry's Web Services and Service-Oriented Architectures, The Savvy Manager's Guide, does something else: it gives you a genuinely useful high-level view.Barry makes a very important distinction: Web services (the term we hear about so much) are connections. Services are what these connections deliver. What is important in the long run are not the connections (Web services) but the goods they will provide (services of many kinds). As Barry and many others see it, the future of software is in the services that will be used to plug information (data) and programming into service-oriented applications.Managing both the connections and the services will be a principal task of IT in the coming years, and it's Barry's contention that it can best be addressed by developing a service-oriented architecture. Much of the book is given over to discussing the nature of software architecture, what it means in the case of services, and how you would go about deciding what kind of architecture to use. This seems like esoteric stuff, but Barry does a very good job of removing excess jargon and inserting real-life analogies to clarify the topics.The author also uses his own experience and point of view to humanize what could be a mind-numbing onslaught of abstractions. I'm particularly happy that he discusses the difficulties of implementing Web services and a service-oriented architecture - a reality check that's sorely missing from many other books.Personally I might quibble with his assumption that the technical difficulties of Web services and particularly the problem of arriving at standards will shortly be resolved. But this is, ultimately, a matter of timing. That Web services are going to be important and probably pivotal for software is generally accepted. Barry does an excellent job of explaining what's involved, why it's important, and how to approach it-necessary background information for just about everybody involved in IT. Highly recommended
Web Services and Service-Oriented Architectures: The Savvy Manager's Guide (The Savvy Manager's Guides)
Frankly, I feel that some reviewers misunderstand the purpose of this book. In my opinion, for the right person, this book is a gem! Any of us who have had the challenge of explaining new and difficult concepts to managers who left technology back in the COBOL days or never were technologists should be grateful.As technologists, we forget just how much intimidating jargon we use and how many underlying assumptions we make when we explain things. As a software architect once said to me, "if I had more time, I'd make it simple." Clearly Barry has taken on the challenge of making it simple, and such efforts are incredibly valuable.
Web Services and Service-Oriented Architectures: The Savvy Manager's Guide (The Savvy Manager's Guides)
As a fellow author of a book targeted at managers, I feel that I have a pretty good understanding of their needs. Doug has done an admirable job of meeting these needs for Web services. This is a book for managers that want to have sucessful Web services projects.Doug starts by motivating the need for Web services with a utopian view of a near future business trip. Then he gives a thorough account of Web services technology basics at a level that even managers whose technical days are long in the past can understand. He ties this account back to the utopian business trip, showing how Web services overcome the technical obstacles to making it a reality.This book really shines in its extensive treatment of how managers can make their Web services projects successful. As a technologist, I have a tendency to underestimate the impact of "soft" project management issues, but Doug has not made this mistake. His years of experience clearly show through in his thoughtful and comprehensive treament of the forces pushing managers to use Web services, the potential obstacles to project completion, and how to overcome them.
Web Services and Service-Oriented Architectures: The Savvy Manager's Guide (The Savvy Manager's Guides)
I've always been a fan of Doug Barry. In the early Nineties Doug Barry focused on OO Databases. He produced a series of reports that compared every feature of every OO database. For awhile these magisterial volumes were the bible for any large company that wanted to buy an OO database. In this case, Doug presented the big picture by organizing the categories a team would use to analyze products, and then covered the details by presenting tables that showed exactly which features or functions each product had.Doug's latest book is Web Services and Service-Oriented Architectures: The Savvy Manager's Guide.(Morgan Kaufmann, 2003). This book is written for architects and managers who are trying to figure out just what Web Services will mean for their organizations. It focuses on describing just what is involved in a Web Services Architecture and then explores the various options companies face as they think about how they might implement such an architecture. A quick glance at the contents gives you an idea of the scope:I. Service-Oriented Architecture Overview1. A Business Trip in the Not-Too-Distant Future2. Information Technology Used in This Trip3. Service-Oriented Architectures and Web Services4. Forces Affecting the Adoption of Web Services and Other Integration Techniques5. Growing Impact of Web Services6. Service-Oriented Architectures and Beliefs about Enterprise Architectures7. Starting to Adopt a Service-Oriented ArchitectureII. Managing Change Needed for a Service-Oriented Architecture8. Change Will Happen9. Tips for Managing Change Issues During DevelopmentIII. Creating Service-Oriented Architectures10. Architectures at Each Stage of Adoption for Web Services11. Architectural Options12. Middle-Tier Architectures13. Revisiting the Business Trip in the Not-Too-Distant FutureIV. Compendium of Software Technologies14. Additional Specification Details15. Quick Reference GuideEarly on, Barry introduces a simple, high-level diagram of an architecture, and then follows through by using it throughout the text with great effect. Many complex options are easily compared or contrasted by a glance at one of the diagrams.Web Services depend heavily on XML and its various standards and Barry confronts that head on by providing an extensive reference guide to all the acronyms that we keep seeing, and that various specifications that tie them together. Anyone new to the world of XML would find it valuable just to buy this guide to get an overview of the world of XML. Most, however, will read the architecture sections, and be grateful that they can flip to the back whenever they want to check on an XML standard of which they are unsure.Given his nice treatment of middleware and the OMG XML standards (XMI, MOF, MDA, CWM), I was sorry that Barry didn't do a bit more to explain the OMG's Model Driven Architecture and explain how it could play a role in the evolving world of Web Service Architectures.This book covers a complex and rapidly expanding field in about 240 pages. Any manager or enterprise architect who is trying to develop an understanding of the basics and figure out the implications of web services should read this book. You won't find a better or more concise introduction to this important new area. Doug Barry has done it again!
Web Services and Service-Oriented Architectures: The Savvy Manager's Guide (The Savvy Manager's Guides)
Throughout the book the author discusses on the same stuff repeatedly.....as multiple parts and chapters. It is a collection of Web services articles narrates the same story of how Web services technology will impact their business strategies and organization. The author written this book exploding a business article and explored his own meaning of Web services oriented architecture.I am bit disappointed after reading the book as the contents does not make a case for a manager..... why you would ever build or use web services, what are its benefits and known issues of Web services, etc. Nevertheless, if you are looking for answers what web services really are (e.g. when to use them, etc.), this book doesn't provide those answers. Think twice before you buy...you may save your money.