# Design Patterns: Architecture of an Autonomous Application

<http://msdn.microsoft.com/en-us/magazine/cc164125.aspx>

- Host: [msdn.microsoft.com](https://links.thingelstad.xyz/hosts/msdn.microsoft.com/)
- Saved: December 11, 2013 (2013-12-11T10:20:33Z)
- Record: https://links.thingelstad.xyz/links/fcce8be3e0d9/
- JSON: https://links.thingelstad.xyz/links/fcce8be3e0d9.json

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

A service should be a completely autonomous application. It's not an island though because you can ask it to perform services for you. But it is autonomous in the sense that it completely controls its data and it denies the outside world direct access to that data or to its objects. The only way to access its goodies is to send it a message asking it to perform a task for you. If it doesn't like the way you ask or who you are, it will refuse to perform the service. Nobody decides this on its behalf; it decides for itself.

## Facts

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

## Saved the same week

- [CQRS](https://links.thingelstad.xyz/links/632211b3b2fc/) (martinfowler.com, December 11, 2013)
- [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)

## Elsewhere

- Wayback Machine: https://web.archive.org/web/*/http://msdn.microsoft.com/en-us/magazine/cc164125.aspx