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
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).
/create
/set-email
/set-preferences
/set-profile-picture
Any ideas?
The text was updated successfully, but these errors were encountered:
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).
Any ideas?
The text was updated successfully, but these errors were encountered: