Web Services Reliability (WS-Reliability)

The Web Services Reliability (WS-Reliability) is a generic and open model for ensuring reliable message delivery for Web Services. It defines reliable message delivery as the ability to guarantee message delivery to software applications - Web Services or Web service client applications - with a chosen level of quality of service (QoS). QoS is defined as the ability to determine the following aspects of message delivery:

  • Message persistence 
  • Message acknowledgement and resending 
  • Elimination of duplicate messages 
  • Ordered delivery of messages 
  • Delivery status awareness for sender and receiver applications 

The WS-Reliability specification provides WSDL definitions for reliable messaging and the message formats specified as SOAP headers and/or body content. 

It addresses the dependencies between the capacity of the messaging nodes (persistence, message processing) and the level of QoS that can be provided.

The OASIS Web Services Reliable Messaging (WSRM) Technical Committee is responsible for the specification.

WS-ReliableMessaging became an OASIS standard in 2004.

Also see . Yes, the names are confusing. See a .


More information: WSRM page on the OASIS website

Context for Web Services Reliability (WS-Reliability)

Home » Articles » Web Services Articles » Web Services Specifications » Messaging » Messaging Specifications » Web Services Reliability (WS-Reliability)

Related Articles for Web Services Reliability (WS-Reliability)

The Savvy Manager's Guide

is also the author of a book that explains Web Services, service-oriented architecture, and Cloud Computing in an easy-to-understand, non-technical manner.

Web Services, Service-Oriented Architectures, and Cloud Computing: The Savvy Manager's Guide

by with David Dick

This is a guide for the savvy manager who wants to capitalize on the wave of change that is occurring with Web Services, service-oriented architecture, and—more recently—Cloud Computing. The changes wrought by these technologies will require both a basic grasp of the technologies and an effective way to deal with how these changes will affect the people who build and use the systems in our organizations. This book covers both issues. Managers at all levels of all organizations must be aware of both the changes that we are now seeing and ways to deal with issues created by those changes.