1. service is self contained and loosely coupled

2. dynamically located and invoked services

3. interface contract (used to access the service)

1. Service is self contained and loosly coupled

The service does not depend on other services to funcion. It has interactions which are loosely coupled, so that they remain independent of other interactions and services. The tasks that the service carries out are pre-determined

For example, a service Address Validation does not need the Check Stock service to function. This means that other applications can call the Address Validation service and reused it. Loose coupling is good because if a service changes its internal mechanism, other services using the change service will not require major changes.

2. dynamically located and invoked services

The services can be located and invoked dynamically. This means if a service moves from one server to another server, it does not matter as its physical location does not matter.

3. interface contract (used to access the service)

An interface is established of how to access the service. This clear interface makes it possible for the service to change and improve its internal processes without affecting the users of the service.

This makes it easy to move from one platform (Java) to another platform (.NET). The interface is kept the same but the mechanisms specific to the platform are updated.

• Printer Friendly
• Email to a friend
• Add to my Favourites
• Download PDF version
• Report Bad Submissions
• Submit Feedback