treees VS domain-driven-hexagon

You may notice the Stack in the dependencies. This is literal stack structure implementation. You can find its code on GitHub.

Scale normalization is performed in this class as well. No other module should be worried about how to get canvas ready. You can find its code on GitHub ;–)

All the configs and settings you can find in the project repo on GitHub.

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