Developing Enterprise Web Services: An Architect's Guide (Paperback)

~ (Author), James Webber (Author)

Editorial Reviews

Product Description

Build Web services with enterprise-class reliability, performance, and value. Web services are transforming IT, and represent a powerful new way to reduce cost and drive top-line growth throughout the enterprise. This book takes a no-nonsense view of architecting and constructing enterprise-class Web services and applications. The authors expertly assess the current state of the Web services platform, offering best practices and new architectural patterns for leveraging the advantages of Web services-and mitigating the risks. This work helps build Web services and applications that meet enterprise requirements for security, mobility, transactions, QoS, workflow, portlets, management, and more. It helps you avoid the "bottomless pit" of application rewriting and maintenance overhead, and architect applications to stay reliable even if some Web services go off-line. It features acale applications to support the inclusion of Web services from multiple partners, and secure private information within Web services environments. It helps you develop high-value mobile Web service applications, and includes a detailed case study. Whether you're an architect, developer, project leader, or manager, this book will help you deliver on the promise of Web services in your real-world enterprise environment.

From the Back Cover

Build Web services with enterprise-class reliability, performance, and value

Web services are transforming IT, and represent a powerful new way to reduce cost and drive top-line growth throughout the enterprise. This book takes a no-nonsense view of architecting and constructing enterprise-class Web services and applications. The authors expertly assess the current state of the Web services platform, offering best practices and new architectural patterns for leveraging the advantages of Web services--and mitigating the risks.

• Build Web services and applications that meet enterprise requirements for security, mobility, transactions, QoS, workflow, portlets, management, and more
• Avoid the "bottomless pit" of application rewriting and maintenance overhead
• Architect applications to stay reliable even if some Web services go off-line
• Scale applications to support the inclusion of Web services from multiple partners
• Secure private information within Web services environments
• Develop high-value mobile Web service applications
• Includes a detailed case study

Whether you're an architect, developer, project leader, or manager, this book will help you deliver on the promise of Web services in your real-world enterprise environment.

See all Editorial Reviews

Product Details

• Paperback: 592 pages
• Publisher: Prentice Hall PTR (November 24, 2003)
• Language: English
• ISBN-10: 0131401602
• ISBN-13: 978-0131401600
• Product Dimensions: 9 x 7 x 1 inches
• Shipping Weight: 2 pounds (View shipping rates and policies)
• Average Customer Review: 4.2 out of 5 stars  See all reviews (13 customer reviews)
• Amazon.com Sales Rank: #846,636 in Books (See Bestsellers in Books)

Customer Reviews

Most Helpful Customer Reviews

10 of 10 people found the following review helpful:

4.0 out of 5 stars Nice Vendor-Neutral Description, December 16, 2003

By	W Boudville (Terra, Sol 3) - See all my reviews (TOP 10 REVIEWER)    (REAL NAME)

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.

5 of 5 people found the following review helpful:

5.0 out of 5 stars Best coverage on the topic, April 7, 2004

By	"ianloe" (New York, NY USA) - See all my reviews

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!

7 of 8 people found the following review helpful:

5.0 out of 5 stars More stuff less chaff !!, July 28, 2004

By	Ajith Kallambella (JavaRanch.com) - See all my reviews (REAL NAME)

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
(...)