These are chat archives for NimbusAPI/Nimbus

19th
Jan 2016
samousavih
@samousavih
Jan 19 2016 00:35
So could you suggest the best way to decide on when the message clean ups from disk should happen?
Andrew Harcourt
@uglybugger
Jan 19 2016 03:33
That depends on the problem we're solving. Unless we're talking very large messages or very long timeouts, it would be safe to just delete the blobs after their expiry date had passed.
It might be worth addin something like that to the large message storage providers - at the moment there are a few loose ends there.
*adding
Does that answer your question?
samousavih
@samousavih
Jan 19 2016 03:36
I have noticed that nimbus already deletes the commands and events which are done using some interceptors, do you suggest such a solution?
Andrew Harcourt
@uglybugger
Jan 19 2016 09:17
It depends on the use case. It will add latency to the command handling if you delete message blobs via an interceptor rather than a background worker, so it really depends on how large your messages are and how long they live.
Drew Freyling
@drewfreyling
Jan 19 2016 11:34
I reckon a background worker might be better
Andrew Harcourt
@uglybugger
Jan 19 2016 11:35
Unless you really (really) need to get rid of them in a hurry, I'd tend to agree.
Argh. Other people's synchronization contexts are doing my head in :p