Queuing works great when you have mostly constant load. Take image resizing, if you size a queue system to handle resizing 10k/images a day it will fall over o

Queuing works great when you have mostly constant load. Take image resizing, if you size a queue system to handle resizing 10k/images a day it will fall over on the day you get a million. If you use serverless it might cost a few extra bucks but you will not have a capacity problem. The million at once thing happens more often then you think, take the case where a website gets a new logo. Now you have to redo the watermark on all the images. Or maybe you want to convert your jpg to webp. You can also use lambdas to process your images on-the-fly as clients request them. We use both pre-process and on-the-fly depending on if we need hashes ahead of time.