From 07ebb8a38bc72f1e7c88ae8889dd16982cb95c63 Mon Sep 17 00:00:00 2001 From: Mauro Servienti Date: Sat, 27 Jan 2024 16:07:47 +0100 Subject: [PATCH] Make it an image --- _posts/2024-01-27-cqrs-and-es.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2024-01-27-cqrs-and-es.md b/_posts/2024-01-27-cqrs-and-es.md index fce0407..25eb769 100644 --- a/_posts/2024-01-27-cqrs-and-es.md +++ b/_posts/2024-01-27-cqrs-and-es.md @@ -24,7 +24,7 @@ In this case, however, the confusion starts from needing to pay more attention t From there, jumping to horrendous models like the following is tremendously easy: -[Horrendous model](https://i.stack.imgur.com/eKU6r.png) +![Horrendous model](https://i.stack.imgur.com/eKU6r.png) I'm not saying that implementing a CQRS architecture using ES is wrong. I'm saying that it's not mandatory—like too many times is presented—and if done without using the right tools, it comes with more downsides than benefits.