Phalcon vs Tornado: What are the differences?
Developers describe Phalcon as "Web framework delivered as a C-extension for PHP". Phalcon is a web framework implemented as a C extension offering high performance and lower resource consumption. On the other hand, Tornado is detailed as "A Python web framework and asynchronous networking library, originally developed at FriendFeed". By using non-blocking network I/O, Tornado can scale to tens of thousands of open connections, making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user.
Phalcon and Tornado can be primarily classified as "Frameworks (Full Stack)" tools.
"Fast" is the top reason why over 57 developers like Phalcon, while over 34 developers mention "Open source" as the leading cause for choosing Tornado.
Phalcon and Tornado are both open source tools. Tornado with 18K GitHub stars and 4.98K forks on GitHub appears to be more popular than Phalcon with 9.74K GitHub stars and 1.78K GitHub forks.
According to the StackShare community, Tornado has a broader approval, being mentioned in 69 company stacks & 16 developers stacks; compared to Phalcon, which is listed in 28 company stacks and 15 developer stacks.
What is Phalcon?
What is Tornado?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.
'm a professional web developer from Vietnam with B.S Physics and Engineering. I'm a Phalcon enthusiast as Opensource. In free time, I was support on forum Phalcon also my forum and contribution core Phalcon.
I think precompiled PHP is the way to go. It saves CPU cycles, RAM and overall I/O. It saves money too. Smaller requirements = smaller bills.
I've tried symfony and zend. Phalcon was easiest to use.
SpreadServe's RealTimeWebServer is built in Tornado. Spreadsheets loaded into SpreadServeEngine instances are projected into browsers using Tornado. Server side recalcs are pushed to the browser using web sockets.
setup an api for a client with tornado backend. incredibly fast and lightweight. unfortunately breaks down when using third party libraries which block internally.
Tornado with Async/Await coroutines provided in Python 3.5 make up for an excellent stack for a micro-service.