NestJS vs Tornado: What are the differences?
Developers describe NestJS as "A progressive Node.js framework for building efficient and scalable server-side applications by @kammysliwiec". Nest is a framework for building efficient, scalable Node.js server-side applications. It uses progressive JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming)
Under the hood, Nest makes use of Express, but also, provides compatibility with a wide range of other libraries, like e.g. Fastify, allowing for easy use of the myriad third-party plugins which are available.. 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.
NestJS and Tornado can be categorized as "Frameworks (Full Stack)" tools.
"Powerful but super friendly to work with" is the primary reason why developers consider NestJS over the competitors, whereas "Open source" was stated as the key factor in picking Tornado.
NestJS 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 NestJS with 17.4K GitHub stars and 1.22K GitHub forks.
According to the StackShare community, Tornado has a broader approval, being mentioned in 69 company stacks & 16 developers stacks; compared to NestJS, which is listed in 12 company stacks and 13 developer stacks.