You will need to think hard about what kinds persistence you need. If you only need a message protocol for sending status updates, with a limited delivery guarantee, then something lightweight like ZeroMQ might be enough and "conveniently" testable as it is a serverless infrastructure. On the opposite end of delivery/consistency of messages, a database provides that, but has much slower throughput and creates a harder single point of failure.

Consider where messages are allowed to get lost - a missing completion message will leave the task in need to be restarted. If the only side effect of this is wasted time, that may or may not be sufficient for you. How important is a crash of the queue server? Can all messages stored in the queue server get lost, or should they be as available as possible?

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.