3 ms·
"every time you deploy new code you need complex and error-prone routines to bring the new process up, have it read the existing state, make sure it's consisten
by sonnyblarney 7y ago
"every time you deploy new code you need complex and error-prone routines to bring the new process up, have it read the existing state, make sure it's consistent with the new features, and if not migrate it to the new format."
Pardon my ignorance ... but wouldn't a stateful model that used mem as true 'cache' not avoid that problem? As if to say the in-memory store is not 'pre loaded' persey, rather, it's loaded incrementally on a on-demand basis from the app itself?
So 'rebooting' has the effect of flushing the cache thats built up over time after reboot, hopefully seamlessly?
Or am I (probably) missing something?
- latch 7y agoYour upstream needs to be able to handle 100% of the load, which could be several orders of magnitude more traffic than it normally has to handle. Handling that huge spike in traffic for, what might not be more than a few minutes a year, can be insanely expensive. Also, you're potentially giving users a noticeably worse experience as you rebuild the cache.
- sonnyblarney 7y agoWell that'd be it then, thanks.