You are right. My target isn’t to remove CQRS from apps that needs it, my target is to remove it from apps that doesn’t need it. If you’re for instance building a real time trading platform with hundreds of writes per second, you obviously have to use CQRS. However, using it when it’s not needed is madness, and I’ve seen it used a LOT when it wasn’t needed.
That might be, but it would probably be difficult to ensure it was complete. Great developers knows when to apply it intuitively, which of course is (almost) never 😊
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Notice how I liked your comment? 😉
You are right. My target isn’t to remove CQRS from apps that needs it, my target is to remove it from apps that doesn’t need it. If you’re for instance building a real time trading platform with hundreds of writes per second, you obviously have to use CQRS. However, using it when it’s not needed is madness, and I’ve seen it used a LOT when it wasn’t needed.
I guess that's fair, though you could have gone slightly further by adding a checklist about when it's actually a good idea to go with CQRS. ;)
That might be, but it would probably be difficult to ensure it was complete. Great developers knows when to apply it intuitively, which of course is (almost) never 😊