loading...

re: Applying Domain-Driven Design principles to a Nest.js project VIEW POST

TOP OF THREAD FULL DISCUSSION
re: @bendix I discussed the article with some co-workers yesterday, very interesting do see someone applying DDD to nestjs. One thing while reading ...
 

Hey @guledali , ultimately it came down to poor handling in the early stages of the development. We had neglected to place strict boundaries around our domain logic so something like a user.service encapsulated a far too large chunk of user logic. We should've spilt the code out into further sub-modules to avoid this.

I think the suggested route recommended by Nest.js definitely works. We find following this DDD approach it keeps clear distinctions between all the different processes our server goes through. (endpoints, business/domain logic, data access etc) Whereas following the typical Angular structure it puts more emphasis on each microservice of your server.

I think there are positives and negatives to both.

Code of Conduct Report abuse