🧠 Ever wondered what really happens before http.createServer() in Node?
I did — and decided to dig way deeper.
While working on my server recently, a thought struck me:
Can I build this from even lower down? Like, handle the raw socket connections myself — understand the handshake, data transfer at the byte level, and have full control over every bit sent and received.
So that’s exactly what I started doing:
✅ Handling raw TCP data streams
✅ Parsing HTTP methods, paths, and headers manually
✅ Building a response engine without relying on the http module
✅ Rewriting my Trie-based router to work directly on top of TCP sockets
Most devs just use express() or http.createServer().
But I wanted to know — what’s really going on underneath?
This deep dive is teaching me:
→ How TCP connections work from the ground up
→ How net.Socket behaves internally
→ How to build custom servers, proxies, or mini frameworks from scratch
Here is the Github Gist for the sample of the new implementation :
Top comments (0)