1. 3

A highly scalable and affordable API that would be able to process millions of images daily.

  1.  

  2. 2

    I use cloudinary just because it makes responsive images so much easier… but I can’t say the ability to scale to millions of images daily would be important to me. Mainly what’s important is that it’s able to do what I want without me ever having to set up imagemagick.

    1. 2

      My scale is much smaller but I am in the process of switching photo hosts for my personal blog, from Flickr to rokka.io (which is paid) in part because of the better control over resizing and other processing. They combine hosting and (cached) image transformation in a way that works for me.

      1. 2

        Thanks for pointing me to rokka! I’m looking to provide an API for resizing and optimization, so they’re of interest to try out and benchmark against.

      2. 2

        I’ve seen a few of these used by commercial projects, often combined with uploading to S3 buckets or hosting. It’s a viable business if you can reach your customers affordably.

        1. 1

          Thanks @pushcx! Quick question, how did those commercial projects justify using a third-party API vs running their own microservice?

          1. 1

            One was a number of years back, there wasn’t yet a beaten path for uploading files from Heroku to S3. The other was in place before I joined, I think they did it rather than fight with ImageMagick.