4 ms·
We've made the mistake of using Flask in production...now we're trying to witch to aiohttp as fast as possible. WSGI is partly to blame. A web technology deri
by pmalynin 10y ago
We've made the mistake of using Flask in production...now we're trying to witch to aiohttp as fast as possible.
WSGI is partly to blame.
A web technology derived from the '93 has no place in 2016.
- philtar 10y agoCan you say more? I'm interested.
- ageofwant 10y agoThe problem is not Flask. Try to understand the technologies you are working with. If you cannot make Flask work for you chances are you won't be able to make it work with aiohttp/whatever. Flask is used in production in sites serving thousands of requests/second.