As more developers apply Command/Query Responsibility Segregation to their projects, many find that it INCREASES the complexity of their systems rather than decreasing it, often without any performance benefits either. Join Udi for a look at where you should, and more importantly SHOULDN’T be using CQRS in your projects.

CQRS can be a powerful architectural approach when applied to the right problems, but it can also introduce additional models, infrastructure, and coordination that increase the complexity of a system.