Notes on messaging : Another important capability of current MDSAL DTCN / DCN is that it’s also retrospective in nature (ie. even when registration happens later after the changes have been committed, late-comers still get the change-notifications) – more like persisted messaging in conventional brokered messaging system. This plays a major role in applications not having to bother much about the “recovery” to rebuild their ephemeral states based on such notifications even if they come up later in their order of booting.
I have been examining few OS frameworks off-late which provide similar capabilities. Will post my comparisons on the list sooner. Something which comes relatively closer in terms of this capability is NATS Streaming (http://nats.io/documentation/streaming/nats-streaming-intro/). Client contract resembles that of Kafka (clients to remember offset of last consumption or they can consume from first (if persistence can tolerate that volume) etc) Apart from location-optimized delivery of something similar to DubSub of Akka, NATS claims support of Req/Reply, Pub/Sub and work-distribution kind of patterns. Of course, NATS is a brokered cluster by itself ☺ Regards Muthu From: controller-dev-boun...@lists.opendaylight.org [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Colin Dixon Sent: Friday, September 30, 2016 11:09 PM To: ODL Dev; controller-dev Subject: [controller-dev] Some DDF notes from 9/29/2016 See attached files for raw notes. --Colin
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
