activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Fernandez <joe.fernan...@ttmsolutions.com>
Subject Re: temporary or durable queue?
Date Mon, 12 Oct 2009 18:16:36 GMT

You may want to consider using Camel to implement the request/reply messaging
pattern in combination with a content based router to route messages to
their respective systems. 

http://camel.apache.org/request-reply.html
http://camel.apache.org/content-based-router.html

Camel makes it a lot easier to implement these messaging patterns and helps
maintain a a clean separation between your application and the underlying
JMS provider. 

Joe
http://www.ttmsolutions.com 



linuca wrote:
> 
> Hi Eveybody!
> 
> I need to build a solution with ActiveMQ. I've been reading a lot, using
> the examples and I think a have a good understanding to start coding. I
> just want to ask for some suggestions first.
> 
> I have to build a web site, where the users will log in and view/modify
> their data. This data is spread in different systems, programmed in
> different languages (supported by ActiveMQ). So the best approach I think
> is the following:
> 
> - one standalone broker
> - synchronous request/reply messaging
> - point-to-point dynamic temporary queues
> - QueueReceiver with timeout
> 
> Is this ok? Or should I use persitent queues? In which scenarios should I
> use which?
> 
> Thanks in advance.
> 

-- 
View this message in context: http://www.nabble.com/temporary-or-durable-queue--tp25826944p25860668.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message