You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we query the events when computing snapshots. A lot of event sourcing frameworks are built around push, i.e. a kafka stream with the event causes snapshots to be computed. There is no turning around and querying the source of truth for the event.
In our case, it would mean, we always precompute snapshots. This reduces the cost of computation at read time. The downside of such a system would be, it won't support reverts.
For some applications, that is not a big problem.
The text was updated successfully, but these errors were encountered:
Currently, we query the events when computing snapshots. A lot of event sourcing frameworks are built around push, i.e. a kafka stream with the event causes snapshots to be computed. There is no turning around and querying the source of truth for the event.
In our case, it would mean, we always precompute snapshots. This reduces the cost of computation at read time. The downside of such a system would be, it won't support reverts.
For some applications, that is not a big problem.
The text was updated successfully, but these errors were encountered: