Hi all. We have a system where we've implemented a pipeline strategy as follows:
1) If the number of messages pending for all actors to a remote host is more than N we flush the message queue to the net 2) If the total number of blocked threads waiting for reading is more then N we flush the message queue to the net 3) We flush the queue also after X milliseconds if we have some message in the queue The idea is move our current architecture to Akka. Taking into consideration that the Akka cluster technology abstracts almost everything related to where the actors are and how many pending messages exist to a particular physical host, etc. my question is: Is the internal Akka net pipeline more or less equivalent to our one or, in case of not, could I plug in something similar our current pipeline into Akka? We've found that the three criteria aforementioned enabled us to adjust our current technology to a wide range of customer requirements. I couldn't find the right way to go on after reading the docs Dispatchers, Routers, and mailboxes, (and also I'm a novice Akka user). Many thanks for your help and suggestions. Best regards, Eduardo. -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
