The Artima Developer Community
Sponsored Link

News & Ideas Forum (Closed for new topic posts)
The Benefits of Loosely Coupled Web Services

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Bill Venners

Posts: 2284
Nickname: bv
Registered: Jan, 2002

The Benefits of Loosely Coupled Web Services Posted: Jan 21, 2003 9:58 PM
Reply to this message Reply
Advertisement
Builder.com has published an article by Jeff Hanson that claims that building and deploying applications using a service-oriented architecture enables loose coupling between components, the benefits of which include location transparency, protocol independence, and time independence.

http://builder.com.com/article.jhtml?id=u00320021211han01.htm&rcode=&page=1

Here's an excerpt:

Jini is a Java implementation of an SOA. Jini provides a platform to build applications using a federation of services that provide the desired functionality. Clients use the Jini platform to find a service via a lookup service, which allows the two components (the service and the code calling the service) to be location transparent. The Jini platform handles where the services are located, so that neither the service nor the code calling the service needs to know where they are.

Another example of how SOA provides loosely coupled benefits is with Web services. Web services represent an increasingly popular SOA methodology for deploying services, enabling location transparency by utilizing registries such as UDDI for runtime discovery. Clients can locate the desired service dynamically by requesting the service from the registry. The Web services architecture provides benefits of loose coupling by providing a mechanism to locate, bind, and call the service dynamically.

Web services allow service developers to implement services using any programming language such as Java or .NET. Web services clients communicate to the service using SOAP, which is XML over HTTP. In addition, Web services developers need not worry about wire-protocol issues since the SOA platforms handle these issues for them.


What do you think of the author's comments?

Topic: Bringing your Java Application to Mac OS X Previous Topic   Next Topic Topic: Jini Community Newsletter

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use