Web Services Explained clearly presents the fundamentals of Web services technology, offers examples of how it can be used for competitive advantage, and shows how it will impact every player in the IT value chain. In this concise briefing, leading analyst and consultant Joe Clabby tells IT and business decision-makers what the Web services revolution really means. Clabby explains how Web services will change the way small, medium, and large-sized enterprises acquire software; how it will change the way ISVs build and market their products; and how it will change the roles of VARs, OEMs, and service providers. He also presents in-depth comparisons of two leading approaches for building Web Services: Microsoft's .NET, and Sun's Java platform.
Book Description
Editorial Reviews
From the Back Cover
Web services for decision makers: strategic insights and actionable recommendations.
- How Web services will transform the way software is built, sold, implemented, and managed
- All you need to know to plan an intelligent Web services strategy
- Risks and pitfalls in current WebsServices architectures
- Detailed guidance for choosing the right vendor
- Up-to-the-minute comparisons of Microsoft's .NET and Sun's J2EE platforms
- Realistic assessments of Web services' impact on ISVs, OEMs, and service providers
Web services will transform the way software is created, sold, and delivered. In this executive briefing, leading analyst and consultant Joe Clabby tells IT and business decision makers what the Web services revolution really means. Web Services Explained clearly explains the fundamentals of Web services technology, offers examples of how it can be used for competitive advantage, and shows how it will impact every player in the IT value chain. It delivers the strategic insights and specific recommendations you'd expect to find only in a $1,000 analyst report, answering the critical questions managers must ask:
- What exactly are Web services?
- How do Web services technologies actually work?
- What are the shortcomings and "gotchas" of current Web services architectures, and what can I do about them?
- What can Web services help me do that I can't do already?
- Who's already using Web services, and what results are they achieving?
- What are the most appropriate Web services applications for my company?
- What questions should I ask Web services vendors, and how should I choose among them?
- Should I commit to Microsoft's .NET platform, Sun's J2EE platform, or neither?
- How will Web services impact my organization?
- How will Web services impact my suppliers and my broader business environment?
If you need to make key decisions about Web services, you need the strategic intelligence that can be found in only one book: Web Services Explained.
About the Author
JOE CLABBY, President of Sensory Virtual, served until recently as Vice President of Platforms and Services at the Aberdeen Group in Boston, one of the top five technology research and analysis firms in the United States. At Aberdeen, he managed a team of research analysts and wrote several of Aberdeen's key reports on strategic technology. His technical background includes 23 years in the IT marketplace, in roles ranging from sales and marketing to program/project management, research, and analysis. He is author of Visualize This: Collaboration, Communication, and Commerce in the 21st Century.
Product Details
Would you like to update product info or give feedback on images?
|
More About the Author
Discover books, learn about writers, read author blogs, and more.
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
10 of 12 people found the following review helpful:
3.0 out of 5 stars
Not,
By
This review is from: Web Services Explained, Solutions and Applications for the Real World (Paperback)
This book contains some useful information, but has several serious flaws. The useful information in the book can also be found in several other books and online sources, including the online excerpts from the book. The marketing hype for this book qualifies as false advertising, in my opinion. For example, "All you need to know to plan an intelligent Web services strategy", "Detailed guidance for choosing the right vendor", and "Up-to-the-minute comparisons of Microsoft's .NET and Sun's J2EE". The book purports to offer a non-technical explanation of topics which are inherently technical. It contains a few simplifications of technical matters which are misleading in important ways. For example: "The use of 'objects' is a fundamental concept in Web services, because it enables the assembly of large, compound applications faster than by today's monolithic methods. And, because programmers do not need to constantly recreate objects from scratch (they just plug in the appropriate object and away we go)..." (pg. 24) Anyone who knows much about software engineering will know that this is very misleading. Code re-use is facilitated by object-oriented methods, but reuse is possible with non-object oriented methods, and is by no means guaranteed to be successful with object-oriented methods (...and away we go). The book defines a Web service as an application or application component which makes use of XML, UDDI, WSDL, and SOAP. UDDI is "a 'registry standard' that allows applications to be listed and located". UDDI would allow applications to find services or components on the web in an automated fashion. Support for and use of UDDI is currently very limited. The author suggests that the current limited use of UDDI is a major drawback for web services in general. This too is misleading: there are many valuable web services which have been and will be implemented without using UDDI. For most current applications, UDDI would be of little value, because the task would remain for an analyst or programmer to determine whether and how the available services might be used. The most serious flaw in this book is the editorial disaster which is Chapter 9, "Should We Adopt .NET, or J2EE?". The 'objective comparison' of these 2 competing platforms for web services begins with excerpts from a white paper by the Middleware Company, which specializes in Java server-side application development. The author describes the paper as "fairly objective", an assessment with which I firmly disagree. Microsoft apparently sent a memo to the author, stating a number of disagreements with the Middleware paper. The author, Mr. Clabby, pastes excerpts from the Microsoft memo, mixed in with repetitions of the previously included material from the Middleware paper, in a confusing jumble. In my opinion, the Microsoft response incorporates some good points. Mr. Clabby should have taken the time to rewrite (and then proof-read) Chapter 9. In the end, the book does not deliver "specific recommendations", but states (correctly, in my opinion) that what any enterprise should do about web services depends very much on the specific circumstances of that enterprise. These circumstances will include the particulars of the enterprise's business, and the readiness of the enterprise's technical staff to deal with web services. One recommendation I would make, and which this book implies but does not state explicitly is that for any enterprise, the time to start learning about web services is probably now. This book can contribute to that process, but parts need to be taken with a grain of salt, and it certainly does not provide "all you need to know"...
Share your thoughts with other customers: Create your own review
|
|
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
