+1 (binding)
Regards
JB
> Le 16 févr. 2021 à 22:12, Havret a écrit :
>
> Hi All,
>
> I have put together a release of activemq-nms-api, please check it and vote
> accordingly.
>
> This release brings NMS 2.0 support.
>
> The files can be grabbed from:
>
+1 for adding a replication backend
+1 for keeping KahaDB intact for stability
+1 for adding the replication as a separate backend adapter (perhaps it depends
and extends activemq-kahadb-store vs direct modification?)
+1 on considering alternatives to ZooKeeper
IMHO— fully-synchronous
Hey JB, I am interested here.
I know many approaches to replication have been tried - with AMQ 5 as well
as Artemis. For example, "LevelDB replicated storage" and "Pure Master
Slave" (where the active broker copied updates to the passive brokers) in
AMQ 5. So I'm curious how the problem is
I like the idea of having a distributed store for 5.x (and Artemis too) but
I don't think it makes sense to mess with KafkaDB at this point as it is
quite stable and I think it would be tough to get it to work properly.
There were a ton of problems with Zookeeper and LevelDB which is one reason
it
Hi JB,
+1 from me in general.
I have to say, i like the idea of separating control plane from data plane,
using zk for topology and leader election. Its something that i think we need
to do in Artemis tbh, too.
Re kahadb in particular i think there were alot of issues, and thats why it
+1 (binding)
Just like to add this is really exciting that nms getting modernised both in
terms of capabilities updating to jms 2.0 features, but also keeping with the
times with .net modern task async interfaces.
Obviously this is just the api, but looking forward to this enabling then the
