Hi dev.to
I’m building SoapJS, a TypeScript framework focused on helping developers create backend applications using Clean Architecture principles with less boilerplate and clearer structure.
It is still pre-1.0, so the API may change, but the core idea is already working:
- domain-first application structure
- use cases, entities, repositories and mappers
- clear separation between framework, database and business logic
- support for Express-based APIs
- MongoDB and PostgreSQL integrations
- generated project structure and reusable patterns
Right now, SoapJS is mainly focused on Express, MongoDB and PostgreSQL, but the goal is to gradually support more frameworks, storages and infrastructure adapters.
The core package is available here:
https://www.npmjs.com/package/@soapjs/soap
I also prepared a demo project showing how it can be used in a real Node.js application:
https://github.com/soapjs/soap-node-demo
I’m preparing a new series of tutorial videos for YouTube, showing how to build backend applications using SoapJS and @soapjs/soap.
SoapJS in 5 Minutes
The series will cover practical backend development, clean architecture patterns, feature generation, use cases, repositories, API routes, and testing — all with a focus on keeping the codebase clean, scalable, and easy to maintain.
At this stage, I’m mostly looking for feedback from TypeScript and backend developers:
- Does the structure make sense?
- Is the API intuitive?
- Would this help you build maintainable backend services faster?
- What would you expect from a framework like this before a stable 1.0 release?
Any feedback, issues, suggestions or criticism are very welcome.
Thanks!
