Saturday, January 14, 2012

Asynchronous messaging for SOA integration

The advantages of asynchronous messaging:
• asynchronous communication: the client doesn't have to wait for the reply
• more reliable than RPI style http web service (e.g. you can use guarantee delivery / durable subscriber patterns)
loose coupling, thus more resistant to change
• more immediate than integration via file transfer
• avoid schema sharing problem and locking problem of database integration style

Here are some of my blogs about asynchronous messaging for integration:

Messaging patterns implementation using Oracle OSB:
* Asynchronous web service using Oracle OSB
* Reliable SOAP over http in Oracle OSB: Point-to-Point Channel
* Event-driven Publish-Subscribe SOAP over http messaging in Oracle OSB
* Request-Reply messaging using Oracle OSB

Messaging patterns for scalability problems:
* Claim check messaging pattern with Oracle OSB
* Message sequence pattern

* How to setup JMS resources in Weblogic via console and WLST Python script
* Asynchronous web service using Java (JAX-WS)

Please share comment.

Source: Steve's blog


A compilation of messaging patterns, a definitive reference, useful also for example to understand the patterns in Spring Integration and other message oriented middleware products:
Hohpe's Enterprise Integration Patterns

A very good book, very practical if you need to use OSB for your work:
Oracle Service Bus 11g Development Cookbook

This book teach you not only about how to use OSB but also about SOA architecting, governance, versioning and many other "life" lessons dealing with SOA projects:
The Definitive Guide to SOA: Oracle Service Bus

No comments: