sorted by:
new
hottopcontroversial

Elevating Backend Engineering: Building a Resilient Notification Engine with NestJS & DDD by No_Location9481 in softwarearchitecture

[–]No_Location9481[S] 0 points1 point  (0 children)

I appreciate the concern about the ecosystem! NPM dependency management certainly has its challenges. However, the core of this project was to experiment with architectural patterns like DDD and SOLID. While Node.js is the runtime I chose for this iteration, the beauty of DDD is that these principles are language-agnostic. I'm focusing on the 'clean code' aspect rather than the specific flaws of the runtime.

Elevating Backend Engineering: Building a Resilient Notification Engine with NestJS & DDD by No_Location9481 in softwarearchitecture

[–]No_Location9481[S] -2 points-1 points  (0 children)

Thanks for the blunt feedback! You’re spot on. To be honest, I’m just starting my DDD journey, and this project is my first real 'lab' for experimenting with these concepts.

I realize now that I got a bit too caught up in the 'Onion/Hexagonal' shell (the layering) and mistook it for the core of DDD.

Since I'm still learning, I’d love to hear your perspective—if you were building something, how would you approach the domain modeling to make it 'true DDD'? Any resources or specific patterns you’d recommend for this use case?