Reformulate your question As to organize the exchange of messages between processes according to the principle mailbox?
I need to organize the interaction between the server and multiple workere. For this I want to have a named message queue that will live independently from the process of consuming it. Ie first Wake up the worker, to spit something in the server queue. Then Wake up the server will read something from the queue and spit something in the worker. He may be dead at this time, rose replied. Etc.
The performance of the queue itself has no value. We need to organize as simply as possible with a minimum of dependencies.
All this is done at the expense of time via SQL database - writing to the table, from whom, to whom, in the consumer database pollin getting the right message. But it seems like this is quite ugly and loading of the empty database queries. I want to message to the consumer pushilis.
What are the options.
RabbitMQ - not able to sort queue, which is not connected consumeri.
Redis does not guarantee delivery of messages (?)
Kafka - like is able, but heavy and slow at the start and generally overkill clear, I have 1 message in half an hour, why for such a Kafka?
ZeroMQ - there are no dedicated broker and a few low-level
As a result, I will certainly do through the database but will suffer in search of a more elegant solution. Please help hall!
Most asked not just to advise that using of the brokers and at least two words to describe the architecture of the objects within it (exchange queue consumer topic etc)