Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • Any tips for good CQRS reference material? I'm wary of CQRS as I've seen it lead to over-architecture and a very buggy system with 2 databases one optimized for queries and the other was the system of truth, but when they got out of sync (which was often), then bugs crippled our team for months. Commented Mar 24, 2017 at 21:39
  • What have you seen? And how did the two models get into out of sync? Commented Mar 25, 2017 at 2:25
  • Some CQRS people advocate 2 separate databases, one used for writes, and the other optimized for reads. We wrote to the write one and published events in order to try to keep the other DB in sync. However, those events were handled by custom code which, when buggy, caused the DBs to be out of sync. This is an example of CQRS gone wrong. Commented Mar 26, 2017 at 17:46
  • "Some"? It should be "most of" as there are two models with two different purposes . This is not CQRS gone wrong, this is how CQRS cuts the bugs in half! Commented Mar 26, 2017 at 18:05
  • CRQS at my former organization caused the number of bugs to increase by a LOT due to bugs in our event handlers meant to synchronize data between the 2 data sources. It's one of the reasons I left that company - we were spending entire sprints to address these bugs. Eventually the company backed away from CQRS. See Udi Dahan's post from 2011 that most people shouldn't be using it: udidahan.com/2011/04/22/when-to-avoid-cqrs Commented Mar 27, 2017 at 12:39