Hello all, One of our Akka projects need some kind of master data in order to be initialized properly. Currently, these data reside on a mysql database instance but we're planning to move it to an in-memory datagrid solution.
So far so good. My problem comes up when these master data change as they obviously might change over time. How do you usually manage this kind of scenarios?. Are you applying some "standard" pattern to solve it?. Currently, we're just sending a message to a broker which the Akka system is subscribed to. Thus, the Akka system is informed about the changes have been produced and can react as a consequence. Any other ideas?. Thanks in advance, Juanjo. -- >>>>>>>>>> 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.
