From d3b21f85ef39b7c3dd27d11fc610e8c8df01170f Mon Sep 17 00:00:00 2001 From: Michael Schnerring <3743342+schnerring@users.noreply.github.com> Date: Thu, 7 Sep 2023 05:33:44 +0200 Subject: [PATCH] Docs: fix dead GitHub link --- docs/guide/durability/marten/event-sourcing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/durability/marten/event-sourcing.md b/docs/guide/durability/marten/event-sourcing.md index 989d82757..fadd0bd34 100644 --- a/docs/guide/durability/marten/event-sourcing.md +++ b/docs/guide/durability/marten/event-sourcing.md @@ -6,7 +6,7 @@ if the Wolverine/Marten integration is applied to your application. Do note that exclusive write locking. ::: -See the [OrderEventSourcingSample project on GitHub](https://github.com/JasperFx/wolverine/tree/main/src/Samples/OrderEventSourcingSample) for more samples. +See the [OrderEventSourcingSample project on GitHub](https://github.com/JasperFx/wolverine/tree/main/src/Persistence/OrderEventSourcingSample) for more samples. That Wolverine + Marten combination is optimized for efficient and productive development using a [CQRS architecture style](https://martinfowler.com/bliki/CQRS.html) with [Marten's event sourcing](https://martendb.io/events/) support. Specifically, let's dive into the responsibilities of a typical command handler in a CQRS with event sourcing architecture: