Skip to content

Commit f8e3d56

Browse files
dgafkagitbook-bot
authored andcommitted
GITBOOK-875: No subject
1 parent ce82d1d commit f8e3d56

File tree

1 file changed

+9
-0
lines changed
  • modelling/event-sourcing/setting-up-projections

1 file changed

+9
-0
lines changed

modelling/event-sourcing/setting-up-projections/README.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -203,3 +203,12 @@ This way if even so Ticket Was Registered failed, when Ticket was Closed would c
203203
{% hint style="success" %}
204204
Each Projection keep track of it's position. Therefore whenever new Event comes in, it knows from which point in Event Stream it should fetch the Events from.
205205
{% endhint %}
206+
207+
There is one more important reason for building Projections from Event Stream, **Projection Rebuilding**.
208+
209+
### Setting up new Projections and Rebuilding
210+
211+
Thanks to Projections ability to build the projection from the Event Stream, we are not bound by time. When we deploy new Projection, it will go over previous Events as part of the projecting process.\
212+
This way we can ability to be able to ship new Projections at any point of time, yet with ability to use all the previous Events from the past. 
213+
214+
Besides that we can rebuild existing Projection, as rebuilding is all about reseting the Projection's position, and start to fetch from scretch. You may read about available actions in [Executing and Managing section](executing-and-managing/).

0 commit comments

Comments
 (0)