4 ms·
One of these things is not like the other. You don't have to choose and there will be cases for both where one is the vastly superior choice. For example: I'd g
by nthcolumn 9y ago
One of these things is not like the other. You don't have to choose and there will be cases for both where one is the vastly superior choice. For example: I'd go with Flask for microservices but django for a CMS. I'm sure some people will argue the more apposite. The nodejs thing is so fragmented and difficult by comparison. Flask's routes are better. django's admin absolutely rocks (still). I guess these face-offs are fun but I don't find them very informative, relevant or meaningful. A weird hybrid though - now that would be cool. Or a SAP killer in django.
- cshenton 9y agoMy apprehension about using flask for microservices is that calls to another microservices are going to block. With NodeJS, the webserver and http libraries are async and mature. Python's really missing a solid async requests library (but async webservers like sanic are getting better).
- nthcolumn 9y agohttps://eng.paxos.com/write-fast-apps-using-async-python-3.6-and-redis https://eng.paxos.com/write-fast-apps-using-async-python-3.6... What do you think?