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 started building StreetJS.
StreetJS is a TypeScript-first backend framework for Node.js, designed to provide the infrastructure needed for building real applications—not just simple REST APIs.
🛒 E-commerce platforms
You can build APIs for:
Products
Categories
Customers
Orders
Payments
Inventory
Authentication
Notifications
And connect the backend to PostgreSQL and external services.
💬 Real-time applications
With WebSocket and SSE capabilities, StreetJS can also be used for applications where information needs to move between the server and clients in real time.
Think:
Chat applications
Live dashboards
Notifications
Collaboration tools
Customer support systems
🎮 Multiplayer games
A backend doesn't have to be limited to business applications.
Game servers need:
Authentication
Player sessions
Real-time communication
Game state
Events
Persistence
Monitoring
These are backend problems too.
StreetJS gives me an interesting foundation for experimenting with multiplayer backend architectures using TypeScript.
📱 Mobile application backends
Flutter, React Native, native Android and iOS applications all need reliable APIs.
A StreetJS backend can provide:
Mobile App
↓
REST API
↓
StreetJS
↓
PostgreSQL
You can then add authentication, validation, realtime communication, background processing and other backend infrastructure as the application grows.
💳 Payment platforms
Payment systems require more than a simple API endpoint.
You need:
Webhooks
Authentication
Validation
Idempotency
Transaction handling
Logging
Error handling
Security
This is also an area where a plugin architecture becomes useful.
For example, instead of putting every payment provider into the framework core, integrations can live in the ecosystem.
🤖 AI-powered applications
AI applications still need a backend.
The AI model might generate the response, but your application still needs:
Authentication
Users
Data
API endpoints
Rate limiting
Logging
Billing
Background jobs
External service integrations
StreetJS can sit underneath that application layer.
The AI is only one part of the system.
🌍 The bigger idea
This is what I'm ultimately interested in with StreetJS.
Not:
"Let's build another Node.js framework."
But:
"Let's build infrastructure that makes it easier to build real software with TypeScript."
The framework is still evolving, and there are plenty of things I want to improve.
That's where feedback from other developers becomes valuable.
If you were starting a new application today, what would you build with a TypeScript backend?
A SaaS?
A marketplace?
A mobile app?
A multiplayer game?
An AI product?
I'm curious what developers in the community are building—and what backend problems you think a framework like StreetJS should solve.
GitHub: https://github.com/hassanmubiru/StreetJS
Documentation: https://hassanmubiru.github.io/StreetJS/