Giter Club home page Giter Club logo

Comments (2)

SimonMacIntyre avatar SimonMacIntyre commented on June 23, 2024

How we should properly reset state in replaying event from X event number?

This is critical.

Off the top of my head, I am wondering how to build around this. Since there are not really hard rules set in stone about projectors being actually linked to specific tables etc.

Otherwise, it seems like the event or projection itself would need metadata linking it to a specific event number, so that something automated could theoretically only delete all projection table entries that are sourced from event >= 5.

Maybe a trait like projectionHasEventSource which adds like... an identifier column linking it to the event creation. It would also require projectors only ever projecting to a single table, I think. Which is not enforced, and requires following this standard.

I'm not sure a graceful way to build this into the package.

A workaround as you already alluded to yourself, might be to just always rely on replaying all events and never replaying a subset. Although it is far more work if you have a table with millions of rows, in theory the eventual consistency final state should be the same in both. So although it is inefficient, it should work to replay all events if you wipe the entire table and ALWAYS have a 1 to 1 link between a projection and a projector. (Maybe snapshotting will be enough for this workaround to function longterm at scale...)

from laravel-event-sourcing.

SimonMacIntyre avatar SimonMacIntyre commented on June 23, 2024

Quote from the docs:

If your projector has a resetState method it will get called before replaying events. You can use that method to reset the state of your projector.

If you want to replay events starting from a certain event you can use the --from option when executing event-sourcing:replay. If you use this option the resetState on projectors will not get called. This package does not track which events have already been processed by which projectors. Be sure not to replay events to projectors that already have handled them.

So it would seem the onus is on us when using --from to be very careful.

from laravel-event-sourcing.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.