From 127806694ece8d2004b49b089e027e212f67eda6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Odd=20M=C3=B6ller?= Date: Fri, 7 Sep 2018 11:58:40 +0200 Subject: [PATCH] Fix bad link to Immutability Changes Everything The current link (http://www.cidrdb.org/cidr2015/Papers/CIDR15_Paper16.pdf) returns 404, removing 'www' (http://cidrdb.org/cidr2015/Papers/CIDR15_Paper16.pdf) returns the correct PDF. --- akka-docs/src/main/paradox/persistence-schema-evolution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/akka-docs/src/main/paradox/persistence-schema-evolution.md b/akka-docs/src/main/paradox/persistence-schema-evolution.md index 0dfb47688f..69adc835b9 100644 --- a/akka-docs/src/main/paradox/persistence-schema-evolution.md +++ b/akka-docs/src/main/paradox/persistence-schema-evolution.md @@ -38,7 +38,7 @@ evolution feel free to submit Pull Requests to this page to extend it. In recent years we have observed a tremendous move towards immutable append-only datastores, with event-sourcing being the prime technique successfully being used in these settings. For an excellent overview why and how immutable data makes scalability -and systems design much simpler you may want to read Pat Helland's excellent [Immutability Changes Everything](http://www.cidrdb.org/cidr2015/Papers/CIDR15_Paper16.pdf) whitepaper. +and systems design much simpler you may want to read Pat Helland's excellent [Immutability Changes Everything](http://cidrdb.org/cidr2015/Papers/CIDR15_Paper16.pdf) whitepaper. Since with [Event Sourcing](http://martinfowler.com/eaaDev/EventSourcing.html) the **events are immutable** and usually never deleted – the way schema evolution is handled differs from how one would go about it in a mutable database setting (e.g. in typical CRUD database applications).