From 1e68c8c989efcb3df4dfaf42fa2c897bc84ef202 Mon Sep 17 00:00:00 2001 From: Ivan Dugalic Date: Sun, 6 Oct 2024 11:19:50 +0200 Subject: [PATCH] formating... --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index bf1febe..375aef0 100644 --- a/README.md +++ b/README.md @@ -118,8 +118,8 @@ stream. Here's how you can do it: 1. Incrementing Stream Version: - Each time an event is appended to a stream, the version of that stream is - incremented. This version represents `the last event` that have been - appended to the stream. + incremented. This version represents `the last event` that have been appended + to the stream. - When appending a new event to a stream, you include the current version of the stream in the event's metadata. @@ -138,11 +138,11 @@ stream. Here's how you can do it: ### Modeling event streaming When appending events to the event store, in addition to appending them to their -respective streams (`eventsByStreamId..`), you can also append them to -the `global stream`. The Key schema for the global stream might look like this: -`events.`. To read all events ordered by event ID, you simply query the -global stream. As all events are appended to this stream, you get a -comprehensive view of all events in the system. +respective streams (`eventsByStreamId..`), you can also +append them to the `global stream`. The Key schema for the global stream might +look like this: `events.`. To read all events ordered by event ID, you +simply query the global stream. As all events are appended to this stream, you +get a comprehensive view of all events in the system. 1. Advantages: