How Uploadcare Built a Stack That Handles 350M File API Requests per Day
1–10 of 42 posts
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#2All I can say is they don't seem to donate Django project.
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#3I find it interesting that these sorts of stacks have tons of moving parts. Maybe it's the nature of highly scalable systems? Or does it come from starting with one particular technology and then having to drag in lots of other things to make it work?
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#4All I can say is they don't seem to donate Django project.
Uploadcare contributes to open source, however. For instance, the fast and production-ready Pillow-SIMD fork is a great example. You can search for "Pillow-SIMD" here for the discussion or check out the original article: https://blog.uploadcare.com/the-fastest-production-ready-ima...
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#5All I can say is they don't seem to donate Django project.
If that's all you can say, don't say it at all.
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#6I find it interesting that these sorts of stacks have tons of moving parts. Maybe it's the nature of highly scalable systems? Or does it come from starting with one particular technology and then having to drag in lots of other things to make it work?
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 :)
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#7350M/day = just about 4K QPS. Is that considered impressive nowadays?
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#8350M/day = just about 4K QPS. Is that considered impressive nowadays?
Assuming most transactions are a largish file transfer it seems impressive. And I assume the transactions aren't evenly spaced, so the peak is likely much higher.
4k qps of DNS, for example, would be less interesting.
Re: How Uploadcare Built a Stack That Handles 350M File API Requests per Day
#9350M/day = just about 4K QPS. Is that considered impressive nowadays?
Assuming most transactions are a largish file transfer it seems impressive. And I assume the transactions aren't evenly spaced, so the peak is likely much higher. 4k qps of DNS, for example, would be less interesting.
In the case of large responses, bandwidth out is a much more interesting metric. I'm sure their number sounds more impressive though.