4 ms·
It would be great to see a cache layer in front of S3, in my experience fetching the original image from S3 will be slower than the actual resizing (regardless
by tbarbugli 5y ago
It would be great to see a cache layer in front of S3, in my experience fetching the original image from S3 will be slower than the actual resizing (regardless of the library used) and that happens at least once.
So ideally something like:
1. upload to s3
2. manipulate image to a friendly size (ie. 2048x2048)
3. write the image to an LRU cache (ie. memcached)
with steps 2 and 3 on a separate go-routine
Besides that, really cool project :)
- orf 5y agoIsn’t that cloudfront?
- tbarbugli 5y agoTypically Cloudfront would sit in front of this service and either serve the requested resource from cache or forward the request to the origin (Imagor) if missing from cache.
- orf 5y agoOr you’d use a cloudfront lambda and combine both?
- underwater 5y agoWouldn't you then be processing images on multiple CDN nodes, instead of just doing it once and serving from multiple CDN nodes?
- gingerlime 5y agoThumbor (with nginx-proxy caching) does that[0] but thumbor itself is python-based. [0] https://github.com/MinimalCompact/thumbor/#minimal-compact-thumbor https://github.com/MinimalCompact/thumbor/#minimal-compact-t...