domain-driven-hexagon VS node-typescript-architecture

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

It's opinionated, and it's self promotion, but this is what I've used for every project of mine since 2020: https://github.com/jbreckmckye/node-typescript-architecture

Self-plug: I wrote this Node / TypeScript port of "clean architecture" to typed, functional JavaScript two years ago - and it's served me well on every production project ever since

https://github.com/jbreckmckye/node-typescript-architecture

Node TypeScript Architecture repo by Jimmy Breck-McKye (https://github.com/jbreckmckye/node-typescript-architecture) as a fan of TypeScript this will be extremely helpful for me to see how to structure a TS based Node app

I would also say that certain practices are invaluable for working efficiently, just as they are in a job. I don't unit test my open source work particularly religiously - to be honest, I don't feel it gives me much more confidence. But I do have a personal architecture (based on ports and adapters, if you're interested), that I stick to because it always allows me to keep my pure logic and IO / effects code strictly separated.

May I share this? https://github.com/jbreckmckye/node-typescript-architecture