newtmq / newtmq-server Goto Github PK

Now, the messages which are sent from publisher is stored only on RAM.
That have a high risk of loosing them. We need the mechanism to store them into storage and that should be hidden user.

The feature of topic message passing is needed for scalability.
About the interface, it is acceptable to comply with rabbitmq-stomp's one for portability.

When multiple processes subscribe to a same queue, messages place a disproportionate on a node.
For the aspect of scalability, this is a problem.

Messages should be delivered to multiple subscriber equally and dynamically.

There is no authentication to identity user.

We have to pay attention to following features to implement

• many kind of authentication mechanisms live together
• An authentication mechanism to use can be switched from configuration

To prevent spoofing and illegal extraction or something security critical control by an unauthorized third party, NewtMQ needs to support SSL/TLS encryption.

Currently, there is no way to know where test is in progress.
Once a processing is hunged up, we don't know where processing is wrong.

To solve it, a test which is in progress should be clearly specified.

The test processing of receivnig topic message might be failure in some case.

output in a case of failure
https://gist.github.com/userlocalhost2000/c8a041d9c5e300fdea02a919d4e0585e

output in a case of success
https://gist.github.com/userlocalhost2000/8ea3f30baba113857dff79101fcd10b7

In these output, I added a immediate extend debug output to know what message is received, which is the line shoewn [subscribe] ....

We need a tool to operate internal processing of NewtMQ, like rabbitmqctl of RabbitMQ.

Current NewtMQ is developed using gcc of C99.
NewtMQ will also support Clang of C11.

Making RPC processing simply, NewtMQ has to have a feature of reply-queue.

For more detail of reply-queue is here.
https://www.rabbitmq.com/direct-reply-to.html

The first release version of NewtMQ doesn't have mechanism of clustering or something analogous to make it more scalable and available.
I think these features are must to use on an environment which requires high-level service quality.