node-typescript-architecture VS Tornado

It's opinionated, and it's self promotion, but this is what I've used for every project of mine since 2020: https://github.com/jbreckmckye/node-typescript-architecture

Self-plug: I wrote this Node / TypeScript port of "clean architecture" to typed, functional JavaScript two years ago - and it's served me well on every production project ever since

https://github.com/jbreckmckye/node-typescript-architecture

Node TypeScript Architecture repo by Jimmy Breck-McKye (https://github.com/jbreckmckye/node-typescript-architecture) as a fan of TypeScript this will be extremely helpful for me to see how to structure a TS based Node app

I would also say that certain practices are invaluable for working efficiently, just as they are in a job. I don't unit test my open source work particularly religiously - to be honest, I don't feel it gives me much more confidence. But I do have a personal architecture (based on ports and adapters, if you're interested), that I stick to because it always allows me to keep my pure logic and IO / effects code strictly separated.

May I share this? https://github.com/jbreckmckye/node-typescript-architecture

I am not expert in these but I thought Tornado's ioloop was readable enough for me to learn more event loops. Mostly, it was being implemented in pure Python.

https://github.com/tornadoweb/tornado/blob/branch4.5/tornado...

(Had to be in 4.5 because the newer versions 5.x and 6.x, it's switched to Python's stdlib asyncio)

I am a bit confused, Tornado is web server like a apache http server, or a framework like django, or both?

For Python, I use Tornado.

tornado? this https://github.com/tornadoweb/tornado ?

I'm writing a Node app that talks to a server that uses Tornado, a Python networking framework. The server uses WebSocket and structured JSON to expose RPCs, like sign_on called with the following message:

I've been using Python's Tornado (http://www.tornadoweb.org/) for years now.

Now on version 6, it's fast, well maintained, mature, and has good docs with readable code.

@bdarnell has done an excellent job maintaining it.

Here's one example:

Tornado supported async style co-routines before asyncio was a thing. Now it uses asyncio under the hood by default -- and it did so with an exceptionally smooth transition.

Tornado is another micro framework aimed at a specific use case: asynchronous networking applications. Tornado is well-suited for creating services that open a great many network connections and keep them alive that is, anything involving WebSockets or long polling. Moreover, It requires Python 3.5 or higher and drops Python 2 support entirely.

How to fix tornado.util.TimeoutError: Operation timed out after 5 seconds on tornado test debug?

Here's an official demo chat app using websocket: https://github.com/tornadoweb/tornado/tree/master/demos/websocket, though you should read the docs on websocket for understanding the code.