Event Sourcing and Retroactive Events?

Up vote 0 down vote favorite share g+ share fb share tw.

I have a need to incorporate retroactive events in my event stream and I'm not sure of the best way to implement it. We need to keep the original event stream unchanged for audit and all of the other standard benefits. The event stream is also temporal in nature, giving us the ability to see the values for any point in history.

I.e. The value of x was 10.00 at 5 pm June 1st. Occasionally we find out on June 5 the value of x as was actually 12.00 at 5pm June 1st.

In this scenario we refer to 10.00 as the 'as-at' value and '12.00' as the as-of value and we track both of these in the event stream. Rebuilding the state for the as-at value is a straight forward query from the most recent snap before 5 pm June 1st and all of the events though June 1st. Where I am hesitant is in rebuilding the as-of state.

If there is an as-of correction to the model then then it should be used by default rather than the as-at, but I can't see any way to determine if there is an as-of correction without reading the entire event stream from the point in time until the present (this can be large) and most of the changes will not matter as they will be related to future changes and not the point in time in question. Is there a different approach I should be looking at here? Thanks, Chris cqrs event-sourcing link|improve this question asked 2 hours agoCCondron862.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.