Has anyone tried this successfully yet? I'm interested in combining the: * Akka Reactive Streams Async API goodness * along with the Actor State-Machine goodness * and the Cassandra Dynamic Partitioning Fault-Tolerant Cluster goodness
I am running into an Architecture understanding issue in that I really like the Cassandra Cluster Gossip solution; but I'm feeling like it would even make sense for my Akka Actors to have a similar solution for the App API level; i.e. instead of having to hardcode IP addresses for Akka Actor Cluster nodes in an Application.conf (which is a hassle on adding-removing Nodes); or having to figure out Startup/Shutdown protocols for an essentially Hierarchical Master-Slave architecture which likely has SPOF issues. Does anyone from Akka Team have any insight into how best to think about putting these elements together -- or if I should be pursuing a different combination of tech that serves the same purpose? THANKs in advance! -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
