# CQRS

<http://martinfowler.com/bliki/CQRS.html>

- Host: [martinfowler.com](https://links.thingelstad.xyz/hosts/martinfowler.com/)
- Saved: December 11, 2013 (2013-12-11T09:46:55Z)
- Record: https://links.thingelstad.xyz/links/632211b3b2fc/
- JSON: https://links.thingelstad.xyz/links/632211b3b2fc.json

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

CQRS stands for Command Query Responsibility Segregation. It's a pattern that I first heard described by Greg Young. At its heart is a simple notion that you can use a different model to update information than the model you use to read information. This simple notion leads to some profound consequences for the design of information systems.

## Facts

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

## Same host

- [Eliminating Sales Commissions](https://links.thingelstad.xyz/links/d5757db2ef50/) (martinfowler.com, February 18, 2013)
- [Rules Engine](https://links.thingelstad.xyz/links/5d583de72c52/) (martinfowler.com, June 11, 2014)
- [Microservice Prerequisites](https://links.thingelstad.xyz/links/a6c927a44535/) (martinfowler.com, September 22, 2014)
- [Testing Strategies in a Microservice Architecture](https://links.thingelstad.xyz/links/2cbf7d965383/) (martinfowler.com, January 22, 2015)
- [DataLake](https://links.thingelstad.xyz/links/c87032b36e6d/) (martinfowler.com, March 19, 2015)

## Saved the same week

- [CQRS, Task Based UIs, Event Sourcing agh!](https://links.thingelstad.xyz/links/e6dffe102c89/) (codebetter.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://martinfowler.com/bliki/CQRS.html