3 ms·
Why Pyramid? Why not Tornado, or better yet Tornado on PyPy (if you don't need any non-PyPy-supported libs)? http://www.tornadoweb.org/ http://www.tornadoweb.
by SkyMarshal 15y ago
Why Pyramid? Why not Tornado, or better yet Tornado on PyPy (if you don't need any non-PyPy-supported libs)?
http://www.tornadoweb.org/ http://www.tornadoweb.org/
http://github.com/facebook/tornado http://github.com/facebook/tornado
Tornado is Python's best counterpart to Node.js, and was battle-hardened by FriendFeed b/f Facebook bought them. Now used by Quora, among others:
http://www.quora.com/Tornado-web-framework/Who-are-some-famous-users-of-Tornado http://www.quora.com/Tornado-web-framework/Who-are-some-famo...
- przemoc 15y agoDue to its nature NodeJS is performance-wise still a better solution than any Python-based one, at least for now. And it's async in core and by rule, thus nodejs modules are async too, yet no async-motto is coupled with Python, so it's much harder to get async-ready libs suiting Tornado. Therefore COTS-wise NodeJS is actually also a better solution. But in the end the most important thing is whether you're more familiar with Python or JavaScript and which solution will be more productive for you. Unless you're going for really large scale project and want to shorten your time by using existing modules, Tornado is obviously as good as NodeJS. Loosely relevant: http://amix.dk/blog/post/19484#Comet-with-node-js-and-V8 http://amix.dk/blog/post/19484#Comet-with-node-js-and-V8
- SkyMarshal 15y agoRight, I know the advantages of Node over Tornado/Python, but my comparison was Tornado vs Pyramid, not Tornado vs Node. Node makes sense for the OP's brief project description, but if you're also considering Python for a "Large scale and quite complex project with possible 500k or more users", why Pyramid and not Tornado?