350M/day = just about 4K QPS. Is that considered impressive nowadays?
How Uploadcare Built a Stack That Handles 350M File API Requests per Day
31–40 of 42 posts
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#32Since it's just a DV certificate from Comodo, have you considered switching to Let's Encrypt? Its automated systems could have helped you automatically update.
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#33It looks like your certificate expired. Since it's just a DV certificate from Comodo, have you considered switching to Let's Encrypt? Its automated systems could have helped you automatically update.
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#34It looks like your certificate expired. Since it's just a DV certificate from Comodo, have you considered switching to Let's Encrypt? Its automated systems could have helped you automatically update.
It's a wildcard certificate, which isn't supported by Let's Encrypt yet.
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#35Earlier quoted context omitted.
It's a wildcard certificate, which isn't supported by Let's Encrypt yet.
Site appears to be hosted in AWS. Lots of free SSL goodness to be had from Amazon as well.
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#36Earlier quoted context omitted.
How so? Obviously they won’t be executing (or likely even analysing) any of the uploaded content. Similarly, browsers should not generally be particularly vulnerable to malicious content being loaded with appropriate MIME types in appropriate containers (e.g. ) It sounds like you should be asking how browsers protect users from malicious content. Perhaps you could elaborate?
Image and Video codecs come under attack quite often see https://blog.sucuri.net/2016/05/imagemagick-remote-command-e... In this context the image manipulation they do with pillow and the underlying libjpeg would be a potential source of vulnerabilities.
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#37That's a great read. I've always been interested in learning how such tech-oriented companies found their initial traction. Are there any blog posts / articles / podcasts about Uploadcare's early days and the search for the product/market fit?
I just got wind of it, we at Uploadcare will soon be releasing an article with more info about the early days :) And, I believe, a podcast or two. Thanks for this question, btw. Would you elaborate on what you would like to know? It'll help us compile a great article, thanks :)
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#38Earlier quoted context omitted.
Site appears to be hosted in AWS. Lots of free SSL goodness to be had from Amazon as well.
It's stretching into off-topic land here, but could you suggest any AWS SSL resources that are worth investigating?
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#39It looks like your certificate expired. Since it's just a DV certificate from Comodo, have you considered switching to Let's Encrypt? Its automated systems could have helped you automatically update.
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#40Earlier quoted context omitted.
It's a wildcard certificate, which isn't supported by Let's Encrypt yet.
Site appears to be hosted in AWS. Lots of free SSL goodness to be had from Amazon as well.
Uploadcare does not have issues with certificates and we're indeed going to switch to ACM for some of the endpoints.