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.

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

Detach aggregate from repository on concurrency error? #37

Closed
andreabalducci opened this issue May 18, 2017 · 2 comments
Closed

Detach aggregate from repository on concurrency error? #37

andreabalducci opened this issue May 18, 2017 · 2 comments
Labels
type/question
Milestone
0.1 - Alone in t...

Comments

@andreabalducci
Copy link
Collaborator

Repository works as Identity Map for aggregates (at requested version).
If a concurrency exception is thrown on save the aggregate became stale and the repository will be stale too.

We can detach the stale aggregate before rethrowing so the client can ask again for a fresh version.
@andreabalducci
Copy link
Collaborator Author

We can enable identity map with a decorator + Repository Factory.

@andreabalducci
Copy link
Collaborator Author

Added the Identity map as decorator, up to the dev to choose what to do.
Default implementation keep the stale aggregate in memory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/question
Projects
None yet
Milestone
0.1 - Alone in the Dark
Development

No branches or pull requests
1 participant
@andreabalducci