[erlang-questions] design pattern question for messaging system

[Jesper Louis Andersen]

On Tue, Jul 22, 2014 at 1:53 PM, Miles Fidelman <mfidelman@REDACTED>
wrote:

> But neither of those feels quite right.  This must be a solved problem,
> but I'm hitting a blind spot.  So... what is the design pattern for queuing
> systems and/or reliable message passing in Erlang?


Make each message a process. Skip the queues. Each message runs its own
state to completion. If you need some kind of capacity constraint, use
something like uwiger/jobs or jlouis/safetyvalve, poolboy, basho/sidejob or
likewise. The trick is to dualize the world since Erlang has no channel
concept which naturally maps to a queue.




-- 
J.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140722/1090636b/attachment.htm>