This is probably the question I get asked most often when I talk about StreetJS.
And honestly?
It's a fair question.
Node.js already has Express, Fastify, NestJS, Hono, Koa, AdonisJS and many other frameworks.
So why build another one?
I'm not t...
When people hear "backend framework," the first thing they usually think about is CRUD APIs.
Create a user.
Update a product.
Delete an order.
Return some JSON.
But modern applications need much more than CRUD.
That's one of the reasons I start...
When I started building StreetJS, I thought the hardest part would be implementing features.
It wasn't.
The hardest part has been deciding what should belong in the framework—and what shouldn't.
At first, adding a feature feels simple.
Need aut...
Building a backend framework alone teaches you a lot.
It also makes one thing very clear:
A framework becomes better when more developers challenge its ideas.
That’s why I’m opening the door wider for developers who want to contribute to StreetJS...
Building a backend framework sounds exciting.
Until you actually start building one.
You quickly discover that routing is probably one of the easiest parts.
The difficult questions come afterward:
How should dependency injection work?
How shou...
Every time I started a new Node.js backend project, I found myself doing the same thing.
Set up routing.
Add validation.
Configure authentication.
Connect PostgreSQL.
Add WebSockets.
Set up background jobs.
Generate API documentation.
Confi...
Multiplayer applications are fundamentally different from traditional REST APIs.
In a typical API, a client sends a request:
Client → Server → Response
A multiplayer game needs something closer to:
Player A ─┐
├──→ Server ──→ Player ...