Use patterns for WS-ReliableMessaging

Links to descriptions of the use patterns that motivate WS-ReliableMessaging. Each use pattern description includes an overview of the business problem, of the technical solution without WS-ReliableMessaging, of the shortcomings of this solution, and of how we can use WS-ReliableMessaging to overcome these shortcomings.

Historically, most business-to-business integration has been implemented on a point-to-point basis. However this situation is rapidly changing and hub-and-spoke is becoming more important, particularly for supply chain use patterns. The point-to-point use pattern is also important because, although the eventual goal might be to implement a business-to-business hub, we might nonetheless begin with point-to-point prototypes and proofs of concept.

For a description of each use pattern, see the following topics:

• Assured delivery for B2B Web services: point-to-point use pattern.
• Assured delivery for B2B Web services: hub-and-spoke use pattern.
• Interoperation with other WS-ReliableMessaging providers: use pattern.

---

Subtopics

Assured delivery for B2B Web services: point-to-point use pattern
Assured delivery for B2B Web services: hub-and-spoke use pattern
Interoperation with other WS-ReliableMessaging providers: use pattern

 

Related tasks

Building a reliable Web service application
Detecting and fixing problems with WS-ReliableMessaging
Learn about WS-ReliableMessaging