-
Notifications
You must be signed in to change notification settings - Fork 140
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
Event retention policy/pruning #271
Comments
I'm afraid that this is not supported. A recommended approach would be give a stream a lifetime same as what gets done in accountancy (accounting period, e.g. year, month, etc.). You can read more about this technique here: https://www.eventstore.com/blog/keep-your-streams-short-temporal-modelling-for-fast-reads-and-optimal-data-retention |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Does commanded currently support event retention policies/pruning of old events out of the box? If not, what are the recommended approaches or best practices for implementing event retention policies with commanded?
The text was updated successfully, but these errors were encountered: