Home > Articles > Programming

Web Services Part 4: Offering Enterprise Web Services

  • Print
  • + Share This
Web services don't help the bottom line unless your customers are willing to pay for them. The enterprise architect must determine whether to use web services synchronously or asynchronously. The challenge is to correctly identify the business needs and then match the technology to those needs.
Like this article? We recommend


The third article in this series, "Web Services Part III: What Are Web Services?," provided some basic terminology used when discussing web services (SOAP, WSDL, UDDI, and so on). In this article, we discuss some characteristics of enterprise-level web services. Future articles will continue exploring related topics, including messaging systems, one of the cornerstone technologies for enterprise integration.

A quick browse of the two web services repositories, XMethods and SalCentral, illustrates that most of the published public web services so far are based on existing information-retrieval services such as stock quotes, weather data, and so on. While these services are interesting, it's highly unlikely that corporations (or even individual users) would pay for these services, since they're too granular.

Broadly speaking, web services can be classified into two categories:

  • Synchronous web services
  • Asynchronous web services
  • + Share This
  • 🔖 Save To Your Account