CQRS has become another casualty of the buzzword culture and the cult of 'shiny things' What started as a collection of some reasonably good principles has now turned into an almost religious mantra for some, with more and more outrageous claims, and almost no basis in fact or experience. Scalability...
"Maybe There is a Better Way" I recently presented at DeveloperDeveloperDeveloper in Sydney, and although my talk was Stuff About CQRS, I opened with the slide My Object Today Is to Make You Think ... 'Maybe There is a Better Way' ( slides here ) The real focus of this was around how...
Today I am not strictly mouthing off strictly about the three things in the title, but more about the side-effects of their joy in a web application. Two things have made me feel dirty while implementing a messaging solution in a web application while adhering strictly to Command-Query Separation. Why...
One of the first questions I had once I decided to hide internal state in my domain was how to code decisions paths based upon the current state of the system. CQRS allows the “C” (command) side to become a client of the “R” (reporting) side, so it seemed logical to consume something like my web reporting...
I have been wanting to pull some thoughts together related to my experience of a project I’ll be releasing in a few months that has pulled from all of these hats. The decision to gradually wade into these waters was driven largely by the increased complexity of the behaviors required by this mission...
I just read a post from fellow devlicio.us'er Billy McCafferty and was considering what influences my own solutions to these concerns (ie, repositories, data transfer, etc) now. There has been an abrupt shift/growth in my thinking this year in how I perceive my domain and how I interact with or scale...