[erlang-questions] design pattern question for messaging system
Jesper Louis Andersen
Tue Jul 22 14:00:42 CEST 2014
On Tue, Jul 22, 2014 at 1:53 PM, Miles Fidelman <mfidelman@REDACTED>
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions