I just gave a presentation on CQRS (Command Query Responsibility Separation) at the Sydney Alt.Net group and have uploaded the slides to SlideShare for you to have a look at.

Overall, it's a pretty simple pattern, but also one that can be quite powerful. It can also be the launching point for getting into Domain Driven Design and a gateway to more advanced architectural approaches such as event sourcing and microservices.

That said, CQRS does not need to be used with those and is a valuable enough on its own to be included in every developers toolkit.

CQRS and what it means for your architecture from Richard Banks