New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Avoid Transaction Conflicts #35

Open

meatballs opened this issue Jan 28, 2022 · 0 comments

Member

meatballs commented Jan 28, 2022 •

edited

Loading

The historic module gets a sequence number and writes that to the events table in a transaction.

In similar circumstances, I've seen high loads cause (probably spurious) transaction conflict errors.

I don't want to reduce the transaction strictness. Instead, I suggest..

The event writing uses a similar process to projections where only a single projector can exist at a given time.

A batch of Events would be written to a pending table as a list in a simple object column.

A writer process starts, checks for any already running and then handles batches of pending event writes.

(this starts to sound a lot like a block chain...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment