> Another option is using some combination of Kafka/Cassandra. This will > require some adapting, handling 2 systems instead of one, possible lack of > sync, writing more code, etc. > Which is actually very much in the spirit of event sourcing and eventual consistency. I'm not sure what kind of data we're talking about here (business dictates what consistency level to pick), however this does sound like a reasonable choice you could for example try out in a smaller scale prototype.
> I do have a feeling that one data store that can meet those kind of > requirements would be very useful. > > My guess so far is that this kind of data store doesn’t exist. Just > wondering if you know of anything like this that might be available in the > near future. > We're not really a database company, so nothing on that front coming from our end :-) I hear the guys working on cassandra have been talking about some kind of "push" mechanism, but on the other hand that would be a very "not database thing to do", so there's very split opinions on that (understandably so). I'd give a small prototype a shot and see it the 2 journals approach is manageable for your project or not. -- Cheers, Konrad 'ktoso' Malawski Akka <http://akka.io/> @ Typesafe <http://typesafe.com/> -- >>>>>>>>>> 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.
