Enterprise SOA

How do web services and enterprise services compare?

On a technical level, enterprise services are web services, based on open standards. An enterprise service must be a web service in order to be callable, whether internally or by business partners, customers, or vendors.

Enterprise services, like web services, work from the standpoint of the service provider and the service consumer. The goal is to abstract all the internal details so that the provider and consumer are completely decoupled in terms of implementation. A service consumer should not need to know any details about how the service provider implemented the service on the back end; all the necessary data should be exchanged in a standard, serialized format. There can be no object references that would break the loose coupling of the provider and the consumer. Service providers and service consumers are completely separate; the provider might be a Python application running on Linux and the consumer might be a .NET application running on Windows Server 2003. Although we will talk about service providers and consumers in ABAP and Java in this chapter and the next, it's important to realize that providers and consumers are completely hardware, programming language, and operating system agnostic.

What enterprise services add is business functionality. A one-off web service might be strategic, but designing an enterprise service asks you to look at your most important business processes and turn those into one or more enterprise ...