Most systems that store state say ORM and publish events are just really broken (in a subtle way). They have the problem of two sources of truth (what if they disagree?)
On Monday, September 1, 2014 6:58:56 AM UTC+1, Ashley Aitken wrote: > > > Thank you Markus for a very useful contribution. > > I too included a link to that architecture diagram in a previous post in > another thread. I think the provision of an "eventbus" for CQRS to > integrate with other bounded contexts on the write-side and, of course, the > read-side is very important and something that the current Akka proposal > lacks. > > My challenge to the Akka team would be to consider how someone could use > Akka for CQRS *without* using event sourcing to persist the actors (e.g. > their state may just be saved to an SQL database). Note that I have > nothing against the current PersistentActor class, it seems great. > > As I understand it though, CQRS is completely possible without event > sourcing aggregate state and I believe most such implementations still > needs some sort of reliable / persistent event store / bus for integration > on the write-side and updating the read models on the read-side. > > -- >>>>>>>>>> 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.
