From 11673749e4f0275d166ce5387bee453dec6f2c77 Mon Sep 17 00:00:00 2001 From: Patrik Nordwall Date: Thu, 10 Sep 2020 15:17:14 +0200 Subject: [PATCH] Link to Replicated Event Sourcing video --- akka-docs/src/main/paradox/typed/replicated-eventsourcing.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/akka-docs/src/main/paradox/typed/replicated-eventsourcing.md b/akka-docs/src/main/paradox/typed/replicated-eventsourcing.md index 52770e4b95..e7024b9ae8 100644 --- a/akka-docs/src/main/paradox/typed/replicated-eventsourcing.md +++ b/akka-docs/src/main/paradox/typed/replicated-eventsourcing.md @@ -37,6 +37,9 @@ to handle this. To be able to use Replicated Event Sourcing the journal and snapshot store used is required to have specific support for the metadata that the replication needs (see @ref[Journal Support](#journal-support)). +The [Replicated Event Sourcing video](https://akka.io/blog/news/2020/09/09/replicated-event-sourcing-video) +is a good starting point describing the use cases and motivation for when to use Replicated Event Sourcing. + ## Relaxing the single-writer principle for availability Taking the example of using Replicated Event Sourcing to run a replica per data center.