domain-driven-hexagon VS express-typescript-skeleton

That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/

Domain-Driven Hexagon - architecture (NodeJS code examples)

Can't use any frameworks or libraries? Seems like a terrible idea tbh. I can suggest this repo https://github.com/Sairyss/domain-driven-hexagon - read "modules" and "folder and file structure" sections for some suggestions on how to structure files using patterns like Modular Architecture, Vertical Slicing, etc. Make sure to read the attached links and check code examples.

This is a reasonable intro, furthermore it points out more resources if you would he interested: https://github.com/Sairyss/domain-driven-hexagon

I’ve recently refactored one of my key domains using nestjs/cqrs and was heavily inspired by this repository.

Not a big one, but explains how to combine architectures like clean architecture, domain-driven design, hexagonal, etc. https://github.com/Sairyss/domain-driven-hexagon

I strongly recommand this: https://github.com/Sairyss/domain-driven-hexagon

Here is an example codebase with architectural patterns described more in details: https://github.com/Sairyss/domain-driven-hexagon

I have been using TsED for a year now and I can say that so far I have not had any problems. It is very comfortable to work with this mini-framework. In addition, the creator provides very fast support and is happy to help with any problems. A few months ago I created a REST API template with hexagonal architecture using TsED.

https://github.com/borjapazr/express-typescript-skeleton

As I say in the README of the project:

This is an opinionated template. The architecture of the code base and the configuration of the different tools used has been based on best practices and personal preferences.

This template does not pretend to have the magic solution to all the problems that a developer may face when creating a REST API using Node.js. This is my contribution, after spending some time on it, to the community. It is an opinionated codebase created based on personal preferences, but also based on the application of best practices.

All criticisms and opinions are welcome, indeed I am very grateful for them. Based on them this could evolve, adapt and become something better. I am sure it will bring something to someone at some point, because even from the worst things something can be learned.

Many thanks to all of you who have taken the time to look at the project.