(It seems not....)

When to use
In my experience, CQRS lends itself to large multi-developer projects that are delivered via an internet based front end or via an automation API (for example a WCF or REST interface) where there is a need to scale the reading and writing independently.

The segregation of the read and write side, and the use of a distinct "definition" class for each handler to use means that development can be done in a highly parallel manner without experiencing "model contention" (the big ball of CRUD ).

Using Azure as a back end lends itself to applications with a non-uniform load (either over time, for example where most updates occur at a particular time of the day or over location where users are connecting from different locations)