activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: Duplicating Large Messages
Date Thu, 06 Jul 2006 15:22:25 GMT
On 7/6/06, Sanjiv Jivan <sanjiv.jivan@gmail.com> wrote:
> How does sending a large message via Active MQ compare to a solution where
> the client just saves the data contents to a database and only send some
> sort of locator id to the recipeints. The recipients which are aware of the
> database can then retrieve the contents by the locator ID. Is this
> effectively the same as the ActiveMQ broker storing the message and clients
> retrieving them? Or is the database approach more efficient with respect to
> memory usage, etc?

JMS is optimised for streaming of data round a network & for dealing
with one-to-many streams such as topics. The database approach is
certainly possible but it introduces unnecessary blocking
request-response and database locking whereas the JMS approach is
non-blocking, typically asychronous and one-way.


> In general, is sending such large messages over a (JMS) message bus
> legitimate use case?

Sure

> Can you describe some use cases where they are doing so
> in production.

Folks often want to send large batch files around in JMS. Though its
usually better to strip the batch file into indivdual rows and send
those instead - but when dealing with legacy systems sending large
files is often useful
-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message