I am curious. Have someone considered using Akka internally for scheduling, clustering, etc. Nifi use internally heavily java.util.concurrent classes. Nifi is carefully designed and implemented so concurrency problems are solved. Still this requires a lot of expertise and it's very easy to accidentally introduce some hard to catch bugs.
Actor model offers relatively easy way to handle concurrency. Also Akka team have done lot of work in clustering area. So maybe NiFi can reuse something? I have some Akka experience and using Actors is a lot safer than using java.util.concurrent classes. But Akka itself is too low level to built business applications directly on top of Akka. Thanks Toivo -- View this message in context: http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/Actor-model-and-Akka-tp1992.html Sent from the Apache NiFi (incubating) Developer List mailing list archive at Nabble.com.
