5 ms·
The only issue with images is where you would want the image to be processed (resized for example), before being published, as S3 quite rightly doesn't carry ou
by bapbap 14y ago
The only issue with images is where you would want the image to be processed (resized for example), before being published, as S3 quite rightly doesn't carry out that sort of function. Using a 2000x2000 image as a thumbnail is not a great idea.
- mbell 14y agoI've been thinking about this as I need to implement it soon. I think I'm going to send to S3 then just send a message to a worker to grab it an resize it in the background. My workers are on different VMs so I need some sort of shared storage. That said I've also considered stuffing the image into redis but that seems gross even though my image volume is low. The other benefit I see in going straight to S3 is that I can use the S3 URL to display the image to the user in context immediately after upload even though it hasn't been resized. The worker can just update the image URL when its done with its resizing.
- deleted 14y ago[deleted]
- williamcotton 14y agoYou should check out http://www.imgix.com http://www.imgix.com