Dr. Sandeep Chatterjee is CEO of Cyndeo, a leading technology strategy and development firm specializing in mobile services and enterprise integration. He is also a consultant for Global Fortune-100 and major not-for-profit organizations including Hewlett-Packard and ACCION International.

Title: Developing Enterprise Web Services: An Architect's Guide

Authors: Dr. Sandeep Chatterjee and Dr. James Webber

ISBN: 0131401602

Sample chapter: SOAP and WSDL

Tell us about the Eureka! moment that inspired you to write this book.

I was speaking at a conference in Sydney when one of the attendees yelled out, "You should write a book." I instinctively answered, "That's a good idea." And that evening I made up my mind to write a book on developing enterprise-class Web services and applications. I immediately knew I wanted to write the book with Jim, who also recognized the market need. Within a month, we had a contract with Prentice Hall. Then, things got difficult: we had to actually write the book.

Does this book fill a need that others have failed to fill?

As anyone who has been to the technology aisle of a bookstore knows, there are a lot of Web services books on the market. Most of these books simply summarize one or two technology specifications. Although there is certainly value in condensing a 400-page spec into 200 pages, developers, architects, and managers need much more. They need to understand which industry standards and technologies are used to address key enterprise requirements for Web services, how each technology works, and, most importantly, the best practices and design patterns for their use. Moreover, since multiple technologies are usually required for building enterprise-class Web services and applications, the inter-relationships between the various technologies and the trade-offs must also be understood and highlighted.

Because both my co-author and I have been developers, architects, and managers at various stages of our careers, we understand the types of information, guidance, and advice that is necessary to help people do these jobs. I think this is why our book has been successful in the marketplace; not only has industry accepted and endorsed the book, it is also the first book on Web services to be adopted into the required curriculum of almost 100 universities around the world.

Why this book? Why now?

For the last few years, companies have been toying around with Web services, and for that a basic understanding of SOAP and WSDL was sufficient. But, recently, things are starting to heat up: companies are realizing the benefits of Web services and they are looking at deploying externally-facing services, whether for consumer access, supply-chain interactions, or tying together various divisions within an organization. For these kinds of deployments, the Web services as well as the consuming applications must be reliable, fault-tolerant, support transactions, provide quality-of-service, implement appropriate security mechanisms, support business processes, allow integration with portals, and so on. Simply using SOAP to make remote invocations is no longer sufficient to meet these "enterprise-class" requirements. Although books exist that discuss one or two of these issues, no book addresses all of these critical issues

• Email
• Print
• Share
  • Slashdot
  • Digg
  • Stumble
  • Reddit
  • Newsvine