Mojolicious vs Tornado: What are the differences?
Developers describe Mojolicious as "Perl real-time web framework". Back in the early days of the web, many people learned Perl because of a wonderful Perl library called CGI. It was simple enough to get started without knowing much about the language and powerful enough to keep you going, learning by doing was much fun. While most of the techniques used are outdated now, the idea behind it is not. Mojolicious is a new attempt at implementing this idea using state of the art technology. 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.
Mojolicious and Tornado can be primarily classified as "Frameworks (Full Stack)" tools.
"Open source" is the top reason why over 13 developers like Mojolicious, while over 34 developers mention "Open source" as the leading cause for choosing Tornado.
Mojolicious and Tornado are both open source tools. It seems that Tornado with 18K GitHub stars and 4.98K forks on GitHub has more adoption than Mojolicious with 2.12K GitHub stars and 498 GitHub forks.
Facebook, TravelPerk, and Zalando are some of the popular companies that use Tornado, whereas Mojolicious is used by WebbyLab, Binary.com, and OANDA. Tornado has a broader approval, being mentioned in 69 company stacks & 16 developers stacks; compared to Mojolicious, which is listed in 9 company stacks and 3 developer stacks.
What is Mojolicious?
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
What are the cons of using Mojolicious?
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.
Web part is fully written on top of Mojolicious. Thanks Sebastian Riedel and all the contributors for the great framework!
Веб бэкенд написан полностью на Mojolicious. Спасибо Риделю и всем участникам за этот фреймворк!
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.