Skip to main content
Article thumbnail
Location of Repository

Do Not Ask for Whom the Server Fails:



reliability, availability and web services The ability to invoke methods or run procedures on computers physically separated from a user’s local machine via some network is not new. This arena of remote computing has been fraught with peril though even when the basic quanta in question has been the entire program to be run. Web services have brought this paradigm of remote computing down to an even finer grain in an attempt to treat these remote programs as if they are integral parts of another program, whether local or remote itself. The reliability and availability of servers is obviously quite important when invoking programs on them remotely and is even more critical when parts of a program make use of web services located on machines anywhere on the planet. If a program that makes use of web services does fail, it would then not be apparent whether it failed due to an internal inconsistency, or whether a part-time computer operator tripped over a cord half a world away, only that the program did indeed fail. The reliability and availability of servers hosting web services is then of utmost importance to the growth and use of web services. Constant availability and perfect reliability are targets that certainly cannot be hit. The question i

Year: 2009
OAI identifier: oai:CiteSeerX.psu:
Provided by: CiteSeerX
Download PDF:
Sorry, we are unable to provide the full text but you may find it at the following location(s):
  • (external link)
  • (external link)
  • Suggested articles

    To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.