# CQRS, Task Based UIs, Event Sourcing agh!

<http://codebetter.com/gregyoung/2010/02/16/cqrs-task-based-uis-event-sourcing-agh/>

- Host: [codebetter.com](https://links.thingelstad.xyz/hosts/codebetter.com/)
- Saved: December 11, 2013 (2013-12-11T09:47:56Z)
- Record: https://links.thingelstad.xyz/links/e6dffe102c89/
- JSON: https://links.thingelstad.xyz/links/e6dffe102c89.json

## From the page (probably an excerpt, not Jamie's words)

Many people have been getting confused over what CQRS is. They look at CQRS as being an architecture; it is not. CQRS is a very simple pattern that enables many opportunities for architecture that may otherwise not exist. CQRS is not eventual consistency, it is not eventing, it is not messaging, it is not having separated models for reading and writing, nor is it using event sourcing. I want to take a few paragraphs to describe first exactly what CQRS is and then how it relates to other patterns.

## Facts

- Kind: [Page](https://links.thingelstad.xyz/kinds/page/)

## Same host

- [Community Server Home Page Controls](https://links.thingelstad.xyz/links/e0c6baa7280f/) (codebetter.com, March 24, 2006)

## Saved the same week

- [CQRS](https://links.thingelstad.xyz/links/632211b3b2fc/) (martinfowler.com, December 11, 2013)
- [The reactive manifesto](https://links.thingelstad.xyz/links/5242b23bfda4/) (reactivemanifesto.org, December 11, 2013)
- [Design Patterns: Architecture of an Autonomous Application](https://links.thingelstad.xyz/links/fcce8be3e0d9/) (msdn.microsoft.com, December 11, 2013)

## Elsewhere

- Wayback Machine: https://web.archive.org/web/*/http://codebetter.com/gregyoung/2010/02/16/cqrs-task-based-uis-event-sourcing-agh/