News for hackers. Stuff that matters.
Re:An Opinionated Clojure CQRS/ES Using Onyx, Datomic, Dynam... by dragonwriter on Thursday February 12, 2015 @02:26PM (#9040791)
> That is the best description of the problem event sourcing tries to solve that I have seen.

Huh. I always thought that the problem event sourcing was trying to solve was more that modeling complex interactive systems through their static state rather than modeling the interactions directly as the principal domain objects is invariably futile. While "we're dropping all sorts of interesting data on the ground" may be one manifestation of that, I think the more common manifestation is "we bear too high of an expense when adapting our information system to changes in business process".

Re:An Opinionated Clojure CQRS/ES Using Onyx, Datomic, Dynam... by solipsism on Thursday February 12, 2015 @02:29PM (#9040806)
modeling complex interactive systems through their static state rather than modeling the interactions directly as the principal domain objects is invariably futile

Now that actually makes sense to someone not already familiar with the context.

Re:An Opinionated Clojure CQRS/ES Using Onyx, Datomic, Dynam... by vosper on Thursday February 12, 2015 @03:30PM (#9041198)
I agree - that was the best explanation of CQRS I've seen.
Re:An Opinionated Clojure CQRS/ES Using Onyx, Datomic, Dynam... by socceroos on Thursday February 12, 2015 @07:56PM (#9042290)
CQRS != Event Sourcing. ;)