3 ms·
So I wrote that blog post, was intended to be a quick little guide for S3 integration. As for your point regarding caching and bandwidth utilization, this actua
by reza_n 11y ago
So I wrote that blog post, was intended to be a quick little guide for S3 integration. As for your point regarding caching and bandwidth utilization, this actually comes up a bit, so its a fairly valid point. A lot of times software (and people) are accessing the same S3 asset, multiple times, all on the same network. So by going thru a local cache, you bypass having to reach all the way back to S3.
- fgsch 11y agoAlso S3 has different costs depending on number of requests and transfer.
- andrewguenther 11y agoThat use case makes a lot of sense. Thanks for the response!
- coleifer 11y agoLame of you not to link my post from yesterday about putting nginx in front of s3. This post seems clearly to be in response to mine. http://charlesleifer.com/blog/nginx-a-caching-thumbnailing-reverse-proxying-image-server-/ http://charlesleifer.com/blog/nginx-a-caching-thumbnailing-r...