Skip to content
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.

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

Hot to make the aggregate thread-safe (suggestions)? #78

Open
weare8 opened this issue May 17, 2021 · 0 comments
Open

Hot to make the aggregate thread-safe (suggestions)? #78

weare8 opened this issue May 17, 2021 · 0 comments

Comments

@weare8
Copy link

weare8 commented May 17, 2021

As far as I understand the aggregates are not thread-safe.

I am looking to see how we could implement a thread-safe aggregate without introducing some distributed locking using DynamoDB or Redis.

An example scenario is if you have an ASP.NET REST API and consider the following endpoints for the same user aggregate invoked in parallel from a front end client it can result in weird results in event data (skipped version, dynamodb streams INSERT and MODIFY events writing the same aggregate ID and Version for different events).

  1. /create
  2. /set-email
  3. /set-preferences
  4. /set-profile-picture

Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant