[rabbitmq-discuss] message/artifact chunking?

[Marek Majkowski]

On Fri, May 7, 2010 at 20:25, Jon Brisbin
<jon.brisbin at npcinternational.com> wrote:
> I'm approaching deploying WARs and other deployment artifacts into my cloud using RabbitMQ (of course! ;) by sending a message containing a URL the consumer could use to download the necessary resource, but I was wondering if I should not so easily dismiss chunking my artifacts and sending them in pieces into the cloud, rather than sending a reference to an HTTP-accessible resource which must be downloaded and deployed?
>
> Does anyone use chunking for sending large objects via messages? Is it better or worse than forcing consumers to download their own resource? How do you keep messages in order and make sure your artifacts don't get corrupted? I've never done async chunking before so thought I'd see if anyone has experience in this area...


Putting a large file over RabbitMQ obviously will work, but I'd say
it's a bad idea. It's just easier to put the big things to some
temporary storage, and transfer only light requests over message bus.

Putting large stuff on the bus (throughput) can probably effect in a
degraded latency. On the other hand, if you aren't worried about
latency it might work - and you correctly identified possible
complications.

Marek Majkowski