asim / emque Goto Github PK

Hi Asim.

I just came by this project searching a simple, easy to use, docker swarm friendly message queue solution.
Many other popular message queues are not suitable for my current job.

I am very impressed for your design. It's what I am looking for.

However, after short review I am not sure but concluded it is long way to go.
If you don't mind I want to share my requirements.

1. Java script client including auto reconnection support.
2. Message requeue support from client.
3. Message persistent for HA; seems now just write only and have no saving path config.
4. Message TTL support (Auto remove on timeout)

Best regards.
Sungkyu Kim.

I have download your code and test it with for a while. It work just fine by the instructions.

But I'm wondering if the unique pattern it's implements is the PUB/SUB.

May be a PUSH/PULL pattern (Push/Pull Pattern). One of those scenario when one or more process are pushing data to the queueue, but each message it's supposed to be handled by one and only one worker.

I have worked with PUSH/PULL on ZeroMQ and it work just fine.

A push pull messaging pattern is defined as a messaging pattern when devices push data to the server and others canpull data from the server. Unlike the publish subscribe systemwhere all devices that are subscribed to a topic get the datawhereas in push/pull devices need to pull the data explicitly.