[Catalyst] A Perl Message Queue?

[J. Shirley]

On 8/24/07, Jesper Krogh <jesper at krogh.cc> wrote:
>
>
> > I don't know if you can do Queing but from Jesper's description it
> > didn't seem like order was important. Seemed to me that he just wanted
> to
> > stash something away and grok it later on.
>
> Thats pretty much the requirement. But it needs to be "fail-tolerant" and
> survive a reboot of the computer without loosing messages.
>
> Jesper
> --


If you require fault-tolerant (reliable message delivery) then you'll need
to have a fail-over system for storage.  Typically, this involves databases
as Perrin posted earlier.

If you do a Master-Master replication setup, you're guaranteed to have
redundancy between the jobqueue and you won't have any loss of data.  If you
only have one server, you at least get the failure when trying to insert the
job rather than it being lost in the ether.

I'm not sure of the other messaging queues others have posted, perhaps they
can address if the recommendations support this requirement.

I can, however, say that TheSchwartz does work and is fault-tolerant (both
in terms of hardware failures and recording if a message/job was unable to
be processed properly).

-J

-- =

J. Shirley :: jshirley at gmail.com :: Killing two stones with one bird...
http://www.toeat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20070824/4e738=
994/attachment.htm