4 ms·
They didn’t actually do what the headline claims. They made a memory cache which sits in front of S3 for the happy path. Cool but not nearly rolling your own S3
by ixtli 1y ago
They didn’t actually do what the headline claims. They made a memory cache which sits in front of S3 for the happy path. Cool but not nearly rolling your own S3
- ramraj07 1y agoI also didnt get why the cache had to be memory and not local name storage..
- jonasdegendt 1y agoOut of curiosity, why? My first thought is, why bother with local storage if your turnaround on video chunks is 2 seconds? What's disk going to add besides a little bit more resiliency in that 2 second time frame? This at the cost of having slower pod startups given you have to mount the PVC, and a small performance hit of writing to a filesystem instead of memory. All moot anyway given that the cameras/proxy allegedly has retries built-in, but interested to hear your thoughts.
- ghm2180 1y ago> What's disk going to add besides a little bit more resiliency Resiliency is the point. How would you protect against machine's loss/crash?
- ramraj07 1y agoreduced cost? you can have same storage in nvme (and for this purpose, sufficient performance) at a tenth or hundredth the cost of the same storage in memory in AWS.
- jrochkind1 1y agoTrue, but, if i'm following, the memory cache has to clone S3 API for existing clients that can't be easily altered. Regardless of what you title it, it's an interesting project report!