There’s something dangerous lurking in your software. Not just the general lurking, murky, ickiness you might expect. Oh no, it’s much worse than that. It’s something specific. Something big; something ugly. There might even be more than one. It can’t decide if it’s angry or hungry or both. All it knows is it’s having a very bad day.
There’s lots of great ideas in this post, but I’m a little afraid of scheduled mutations like this. Mainly because it would be hard to recover the correct state if there was an issue with setting them. How would you known which ones to re-set?
Also because it’s a kind of temporal coupling - of the business rules changed from 1 year to 2, it would be quite sticky.
The expiry means we can’t get away with updating on write - I suppose we could do a JIT update on read? At least then we can control the expiry time.