3 ms·
presumably the proxy backend is stateless
by blibble 4y ago
presumably the proxy backend is stateless
- deleted 4y ago[deleted]
- loeg 4y agoAt the end of the day it has to store, consolidate, and present that state to the service's consumers, so there is state somewhere.
- TeMPOraL 4y ago> there is state somewhere Yeah, on third-party code hosting platforms :). And maaaaaybe in some short-lived cache somewhere. I mean, why spend on storage and complicate your life with state management, when you can keep re-requesting the same thing from the third-party source? Joking, of course, but only a bit. There is some indication Google's proxy actually stores the clones. It just seems to mindlessly, unconditionally refresh them. Kind of like companies whose CI redownload half of NPM on every build, and cry loudly when Github goes down for a few hours - except at Google scale.