zlacker

>>mpweih+(OP)
Does anyone know a good, low overhead out-of-process message queue, that's lightweight enough that it can be useful for communicating between processes on the same machine, but if necessary it can scale beyond it? In case of a single-machine product that comprises of several services, a message queue can sometimes be useful for pull model, but adding RabbitMQ to the stack makes installation and ops much more complex than customers deem acceptable.

I know some people use Akka with Persistence module, but I would welcome other alternatives.

>>polski+BF
Guess it depends on the definition of "queue". Potentials:

  - https://nsq.io/
  - https://nats.io/

>>gizzlo+dJ
Seems like NATS streaming would fit my case - have you heard of any real world deployments that use it ? Are there any larger issues that don't make it a good choice ?

>>polski+qp1
NATS Streaming is not as well tested and has some design issues that make scaling hard. NATS itself has a new version 2 that has a protocol update and NATS Streaming should follow with a new design as well, but I would recommend other options if you want persistence.

>>maniga+XD1
Can you share some details or point to articles describing the design issues with NATS streaming?

>>tuxych+0N1
See the other comment but this is a good post/series: https://bravenewgeek.com/building-a-distributed-log-from-scr...