Friday, September 20, 2013

SOA JMS Adapter Vs AQ Adapter

All of them are based on Asynchronous Messaging. All of them uses Queues and Topic to consume..But the datasource from which they consume or produce differs..

1.MQ consumes the topic and queues frm the IBM MQ Server
2.AQ uses an Oracle Database
3.While a JMS Adapter uses File,Memoery and also the DB persistence as AQ.

AQ is a Oracle implementation of their Queue messaging; Advanced Queueing. The same has IBM with their MQ and like others. These implemenations are specific of the Vendors.

JMS is an implemenation of a messaging system based on Open Industy Stanards. The messages send via JMS are based on a persistence storage, the message must be stored/retrieved from a persistence layer. This can be the file-system or based on Oracle AQ, IBM MQ or others.

The SOA Suite supports messaging based on JMS (JMS over MQ or JMS over AQ) or use the messaging directory out/in of AQ or MQ.

Scenarios:
Go for AQ when using Oracle Advanced Queueing (the database stuff).
Use JMS when using JMS (in memory of file queues)


Oracle Advanced Queuing (AQ): (Database stuff)
Oracle Advanced Queuing (AQ) provides database-integrated message queuing functionality. It is built on top of Oracle Streams and optimizes the functions of Oracle Database so that messages can be stored persistently, propagated between queues on different computers and databases, and transmitted using Oracle Net Services, HTTP, and HTTPS. Because Oracle AQ is implemented in database tables, all operational benefits of high availability, scalability, and reliability are also applicable to queue data.

Related Posts Plugin for WordPress, Blogger...