RoQ next phase Plan & priority definition

[Sabri Skhiri]

Dear all,

We are soon reaching the beta release and it is time to plan the RoQ phase II for the release 1.1. I would like to propose different things to implement and to have a discussion about which of those you think it worth investing:
1. Management console re-writing
2. HA: HA of the roq modules and message storing (with check pointing as described in the future work page on the wiki)
3. Subscriber partitioning
4. Security mecanims for ensuring that a publisher will not be re-allocate between the same exchanges (re-allocation cycle detection)
5. Elastic integration with right scale/Amazon/OpenStack
6. A set of connectors: Storm, JMS, rendez-vous, Twitter, FCBK, etc.
 
Have you got any other propositions?

Sabri.

[Sabri Skhiri]

Updates:

1. Management console re-writing
2. HA: HA of the roq modules and message storing (with check pointing as described in the future work page on the wiki)
3. Subscriber partitioning

4. Security mechanisms for ensuring that a publisher will not be re-allocate between the same exchanges (re-allocation cycle detection)

5. Elastic integration with right scale/Amazon/OpenStack
6. A set of connectors: Storm, JMS, rendez-vous, Twitter, FCBK, etc.

7. Message QoS: persistence of messages
8. Exchange in C++: re-implementing the exchange for better performance
 
I have updated the page https://github.com/roq-messaging/RoQ/wiki/Roadmap-&-Milestones

Do not hesitate to vote !

Sabri.

[Sabri Skhiri]

Priority 1:

1. Management console re-writing
2. HA: HA of the roq modules and message storing (with check pointing as described in the future work page on the wiki)

4. Security mechanisms for ensuring that a publisher will not be re-allocate between the same exchanges (re-allocation cycle detection)
5. Elastic integration with right scale/Amazon/OpenStack

8. Exchange in C++: re-implementing the exchange for better performance

9. validating the high number of pub/sub without problem of sockets
10. Use case and future direction workshops

Priority 2:
3. Subscriber partitioning