From a5b6677fb2d3e1be0c9239b5c56642832d120354 Mon Sep 17 00:00:00 2001 From: Vitalii Dasaev Date: Fri, 9 Mar 2018 23:31:37 +0300 Subject: [PATCH] Update cqrs.md (#447) Changed link to section #event-sourcing-and-cqrs --- docs/patterns/cqrs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/patterns/cqrs.md b/docs/patterns/cqrs.md index 8395b28375a..79619688231 100644 --- a/docs/patterns/cqrs.md +++ b/docs/patterns/cqrs.md @@ -63,7 +63,7 @@ Consider the following points when deciding how to implement this pattern: - Consider applying CQRS to limited sections of your system where it will be most valuable. -- A typical approach to deploying eventual consistency is to use event sourcing in conjunction with CQRS so that the write model is an append-only stream of events driven by execution of commands. These events are used to update materialized views that act as the read model. For more information see [Event Sourcing and CQRS](https://msdn.microsoft.com/library/dn568103.aspx#EventSourcingandCQRS). +- A typical approach to deploying eventual consistency is to use event sourcing in conjunction with CQRS so that the write model is an append-only stream of events driven by execution of commands. These events are used to update materialized views that act as the read model. For more information see [Event Sourcing and CQRS](/azure/architecture/patterns/cqrs#event-sourcing-and-cqrs). ## When to use this pattern