Introduce queues to improve inter-bot communications

[neomatrix369]

As the project started off as a demo project, inter-chatbot communications are not the most optimum.

Also if we would like to introduce a frontend via #17 then the interactions would be best handled by a queue.

Spikes and prototypes to come up with a queue would be a great start, some examples of queues could be:

• JMS
• ActiveMQ
• RabbitMQ
• Kafka

Although for all intent and purpose of this project a simple queueing library is more than enough - a simple approach is a good start.

[yugoccp]

Hi @neomatrix369! Wish to have clearer idea about this issue.

Thought the simplest architecture to satisfy most of the current features:

1. Chatbot produces message to message.post queue
2. Mediator consumes message from message.post queue
3. Mediator wait 4 sec, log message and post to message.display queue
4. Chatbot consumes messages from message.display queue

Mediator have some control over the conversation, such as wainting 4 sec to display next question and log messages

Drawbacks:

• Eventually a chatbot can reply itself

[neomatrix369]

Nice idea, let's think about it while also taking a couple of steps back and do the following:

• come up with a simple queue system ourselves between the chatbots and connecting world (improving the current logic)
• then make another solution using some lightweight queues library
• try to do a spike via RabittMQ or ActiveMQ
• try a spike with Kafka and zookeeper

Let's do a spike first and then move to a complete solution driven by tests