serverless-image-handler VS base65536

AWS Suggests this if you want to do regular lambda + CF cache and they say it is production quality: https://github.com/aws-solutions/serverless-image-handler

I use imgix to resize images on the fly, which I recommend, but given the large amount of images you have it may not be cost effective. You could look into running your own: https://github.com/aws-solutions/serverless-image-handler

It looks like there’s a ‘standard service’ for video media: https://aws.amazon.com/elastictranscoder/ but actually for jpg you might need to do something a bit more bespoke. You could deploy a ‘serverless’ lambda function to do this conversion and write the S3 urls to a database after: https://github.com/awslabs/serverless-image-handler. Looks like it uses SharpJS: https://sharp.pixelplumbing.com/. In the past I’ve used ImageMagick on compute instances: https://imagemagick.org/script/index.php

base 65536 might be the direction to look for because it uses the whole range of UTF 32 encoded text.

Sorry, I edited the post concurrently with your comment - it now points to Base2048, the link I meant to post, which actually should work - rather than https://github.com/qntm/base65536 (which I think you're commenting on).

base65536

There's always base65536

https://github.com/qntm/base65536

Yep! Or if you're feeling especially nasty, base65536 (which may not always encode into a URL...)