dmitrymukhin

<3

Cloudinary, Imgix, Uploadcare (which I' working for) and others save you money because you don't have to develop and maintain these moving parts. You have to constantly check what's happening with browsers, what formats/encoders are available and which are the best etc.

It's classic build vs. buy dilemma. In majority of cases it's much more cost effective to buy.

BTW, Uploadcare doesn't charge for file processing at all, only for CDN traffic. So you can create as much image variants as you need.

btw Uploadcare is also doing image processing on the fly for you :)

can you post a link to the rule, please

Cloudinary, Uploadcare, Filestack, Transloadit

Open source Thumbor.

Short answer is:

- believing in your own service - perseverance - fanatical customer support

This helped us to stay focused and our happy customers brought us new happy customers. We didn't know much about marketing in the beginning.

It's Heroku for Stackshare: https://stackshare.io/stackshare/stackshare

Uploadcare does not have issues with certificates and we're indeed going to switch to ACM for some of the endpoints.

It's not that hard to get high numbers with AWS, indeed :p

The hard thing is to make it cost effective. To that end I can proudly say that AWS bill is not in the top list of Uploadcare expenses.

I totally agree, but this was one of the requirements of the editor to have a "good marketable" headline. And we have to admit that this worked quite well.

On the other hand I feel that the article is very light and is indeed more for layman audience :) In depth one would be 10-15 times longer (and 100 times harder to write).

Cached/uncached file delivery is close to the universal 80/20 ratio. Cached operations are not included in that number.

Unfortunately, I can't say anything more than that.

Oh the irony.

In the article we tried to convey the main idea behind that — take the best tool for the job at hand. There's no "one size fits all" framework or product to put you money on. It's much easier to handle this zoo than making something do that it's not supposed to.

Furthermore, to get high scalability, you have to make things as loosely coupled as possible. This means you're up to making some choices.

Hope that makes sense and answers the question :)

I thought this was in article already :)

well, there's svg) as for raster, first, I don't think you can have infinite sizes as in vector in feasible manner, second, progressive jpegs are already there, maybe we need to teach clients to stop downloading more info when there's enough for certain container.

wondering if there is some interest in getting this as a hosted solution or as an AWS AMI

the problem is that some native apps are just wrappers for web apps and still fail miserably.