> > I'd write to a primary journal and use the (Akka) query side to populate > the other journal. Yes they may be a bit behind, but depending on needs > that could be optimised (query side could be pushed to). >
We've discussed this option - write events to Kafka, then pull the events from Kafka and push them to Cassandra (or any other suitable data store). One possible issue with such a set up is incorrect recovery, as actors will be recovered based on the data in Cassandra and it will not contain the latest events. This risk is not acceptable in our case. We'd prefer to have the most updated data - system's point of truth - in Cassandra and then publish it via Kafka. > Have you looked into Akka Persistence Query yet? We implemented something > for leveldb this week that might inspire you (I'm on my phone, hard to find > links) - check prs about eventsbyperistenceid. > I have, looks very interesting, we'll definitely try it out soon. Thanks! -- This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this on behalf of the addressee you must not use, copy, disclose or take action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply email and delete this message. Thank you. -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
