By: Rinat Abdullin
Nice article, I really liked the concise rule of collaboration in CQRS – straight to the point. Potential typo: “After understanding all that and you find a true single-user-only-thing,” BTW, Occam’s...
View ArticleBy: Remco Ros
Really nice post Udi. Funny side note: No matter what numeric base you take, 1 + 1 will always be 2
View ArticleBy: Josh Schwartzberg
Great post. So basically 2 or more users working on the same data warrants CQRS ? Before jumping right into CQRS and eventual consitency, Pessimistic Locking with CRUD can work well in small (5-10...
View ArticleBy: Diogo Mafra
Great post!! I would like to see more people asking the real question, the WHY behind the problem. And also realizing that, there is not only one solution for everything. By asking the why, we gain a...
View ArticleBy: James Pelletier
So often when I start asking why I get ushered out the door… I’m having trouble making people see these are important questions.
View ArticleBy: Tarek
Josh, “Pessimistic Locking” is interpreted in different ways. Merely locking the record while you’re updating it does not really solve the problem if the other concurrent request will be served right...
View ArticleBy: Chris Nicola
Udi, this is all very interesting and as a fairly pragmatic software developer I’d never assume CQRS is a silver bullet solution for anything. However while in this post you have given yet another...
View ArticleBy: Josh Schwartzberg
Tarek, More explicitly, if you do not allow the second user to click the “begin editing” button for an entity, they would never accidently do some work and find out that all is lost when they go to hit...
View ArticleBy: Alex Simkin
Base 10 is not a ubiquitous best practice. In fact it is. 10 (one followed by zero) is ALWAYS base in any positional numbering system. So you should have been using word “ten” not symbol 10.
View ArticleBy: Frank Quednau
Reminds me of the fact that there is a formula to calculate an arbitrary digit being at the nth position of the number Pi without calculating the preceding digits – however, it only works with the...
View ArticleBy: Tarek Nabil
Josh, What you’re describing is some times referred to as a “Pessimistic Offline Lock”. Although it is suitable for certain situations, it has its limitations, especially in web applications, where...
View ArticleBy: ste
How is “true single-user-only-thing” defined? Does it mean, that only a single user views or edits certain data at a time but there could be some kind of process which passes the data from one user to...
View ArticleBy: Charlie Barker
I like this rule of thumb it is a good sanity check. I find that once I have a sufficient understanding of the business problem building a solution becomes straightforward. The tricky part is building...
View ArticleBy: Adam
Great article. Although you are explicitly talking about CQRS I feel like this applies on a much broader scope of “right tool for the job.” Too many times people find a hammer that they like and decide...
View ArticleBy: Kevin Jordan
“CQRS is actually in danger of reaching “best practice” status at which point in time people will apply it indiscriminately with truly terrible results.” One does get this impression by the amount of...
View ArticleBy: Eben
Nice post! I do think, however, that as time goes by certain techniques *can* be used in *all* situations but it may be that in some applications it is overkill — as would be the case in a ’small...
View ArticleBy: Matt S.
I’m still having a hard time wrapping my brain around this technique when it comes to my users’ (primarily website users) need for instant gratification. They expect to see their recent edits applied....
View Article
More Pages to Explore .....