Survey: what are you using 'sharp' for?

I’m truly humbled by the recent surge in support for sharp.

Whilst ⭐ and the trending status they bring are both amazing, thank you, the real measure of open source success is happy users.

I’d love to find out more about how you or your organisation are using (or plan to use) this module.

Feel free to add a comment with details of who you are, what you’re doing with it and why you chose it. Alternatively let me know via @lovell on Twitter.

Thank you!

[wmertens]

Very interesting - another aws blog has a post on using sharp and lambda@edge: https://aws.amazon.com/blogs/networking-and-content-delivery/resizing-images-with-amazon-cloudfront-lambdaedge-aws-cdn-blog/

[Goues]

@wmertens We might open source in the future but not at the moment - there is a lot of stuff specific for our database and integration with other services that would be time consuming to separate.

In general, duplicate uploads are handled by file hashes. You do not upload to a bucket images are served from, but to an upload bucket. Put Event is then send to SQS for ingesting (another lambda) where we take an MD5 of image and create a rename a file accordingly. Duplicate upload means an image of the same md5 name already exists in public bucket. There is also a Dynamo DB table for storing status (uploaded cannot use uploaded image until it is igested and confirmed).

On the smaller project, this pipeline is downscaled by taking care of duplicates at all and users have limit of stored MB of images, so they are themselves responsible for not creating duplicates.

We went with this solution after trying out lambda@edge on cloudfront, because it would allow for no redirects at all, but edge lambdas are not good with binary data and large response bodies so it didn’t turn out well.

There is a good “how to start” here: https://aws.amazon.com/blogs/compute/resize-images-on-the-fly-with-amazon-s3-aws-lambda-and-amazon-api-gateway/