# The reactive manifesto

<http://www.reactivemanifesto.org/#the-need-to-go-reactive>

- Host: [reactivemanifesto.org](https://links.thingelstad.xyz/hosts/reactivemanifesto.org/)
- Saved: December 11, 2013 (2013-12-11T10:20:03Z)
- Record: https://links.thingelstad.xyz/links/5242b23bfda4/
- JSON: https://links.thingelstad.xyz/links/5242b23bfda4.json

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

Application requirements have changed dramatically in recent years. Only a few years ago a large application had tens of servers, seconds of response time, hours of offline maintenance and gigabytes of data. Today applications are deployed on everything from mobile devices to cloud-based clusters running thousands of multicore processors. Users expect millisecond or even microsecond response times and 100% uptime. Data needs are expanding into the petabytes.

## 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)
- [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://www.reactivemanifesto.org/#the-need-to-go-reactive