News for hackers. Stuff that matters.
Re:Flask 0.11 Released by keshab on Sunday May 29, 2016 @09:36AM (#11796307)
I am sorry, but it seems that Pinterest is written using Django.

https://www.djangoproject.com/start/overview/

Re:Flask 0.11 Released by tomnipotent on Sunday May 29, 2016 @10:04AM (#11796399)
Re:Flask 0.11 Released by dempseye on Sunday May 29, 2016 @10:32AM (#11796479)
That page does not support the statement that they moved off Django to Flask.
Re:Flask 0.11 Released by tomnipotent on Sunday May 29, 2016 @01:44PM (#11797332)
It further links to this post:

https://www.quora.com/What-is-the-technology-stack-behind-Pi...

> They started with Django but moved out of Django and currently use 'home grown framework on top of Flask'.

Re:Flask 0.11 Released by lrem on Sunday May 29, 2016 @11:14AM (#11796615)
But it supports that they do use Flask.

> Presently, the API does over 12 billion requests per day, all in Flask.

Wow, that is 138kqps. Not something that would strike me as your typical Python workload.

Re:Flask 0.11 Released by ubernostrum on Sunday May 29, 2016 @05:56PM (#11798416)
There are lots of those lying around.

I don't know if it still is, but when I was at Mozilla the service that every instance of Firefox around the world hits to do the version/extension-compatibility checks was backed by Django, and was at something like 15k req/s served. Firefox has gained some market share in the four-ish years since I got that number, so probably larger now.

Re:Flask 0.11 Released by nly on Sunday May 29, 2016 @11:55AM (#11796774)
Whacking great big CDNs in front of your infra will do that.
Re:Flask 0.11 Released by lrem on Sunday May 29, 2016 @12:08PM (#11796835)
What exactly a CDN can do to increase the qps throughput of your backend? I thought it's used to reduce it...