-
Notifications
You must be signed in to change notification settings - Fork 115
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
Cleaning Snapshots #100
Comments
At the moment, I have muted other stores tests, because I don't know if I will be able to implement it in every stores. |
I would do the cleaning in combination with cqrs-domain. |
It would be nice if you could do the mongodb implementation too (just if you want)... |
I've done a few things:
Let met know if you see other things before submitting the PR |
Seems ok, |
haha 😅 I also need to make some real world tests on my project, with a huge amount of snapshots, to see if everything is ok. |
done ! |
v1.12.0 |
ok thanks @adrai ! |
no time to contribute atm, but just want to leave a quick thank you! |
@rehia I had to exclude elasticsearch the search function has some errors (no idea why) |
I started a conversation in the issue #94 to talk about overall performance improvements.
I was talking about a feature, where the snapshots are cleaned automatically.
So I started an implementation here https://github.com/rehia/node-eventstore/tree/clean-snapshots, where I implemented the snapshot cleaning feature for in memory and redis stores.
I still need to make some wider tests, but I also wanted to have your opinion on this feature.
I basically added a new option : max snapshots count, which indicates how many snapshots you want to keep at max. So if the value is 5, and you have already 10 snapshots, when you will create the next one, the 6 oldest will be deleted. By default, of course, none is deleted, as it is actually the case.
What do you think about this feature ? Is this the way you think snapshot cleaning can be done ?
Thanks for your feedback
The text was updated successfully, but these errors were encountered: