Hi, as a user of ActiveMQ running it productively I can only stress the importance of introducing a new scalable broker core. Challenges like cloud, IoT cry for scalability and that's where other brokers like RabbitMQ create a lot of momentum.
Personally, I don't get the point why having HornetQ as a subproject like ActiveMQ Apollo is a problem - as I understand this was the original intent. Did anyone bring up this point when Apollo was introduced? I'm focused on the value for the users and would love to see HornetQ, ActiveMQ emerge as one broker that can really compete going forward. Joining forces makes a lot of sense to me. If projects get separated then compatibility, migration topics might get less important. Best Regards, Oliver -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-HornetQ-ActiveMQ-s-next-generation-tp4693781p4694192.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
