use a slightly more nested folder structure about book HOT 6 CLOSED

re where to put uows and deduplicate, am sure you can figure something out. uows would have different repositories for different contexts, but some sort of shared base class could be useful.

from book.

I suppose that allocation is a bounded context. If I have another context like, orders for e..g, should I have another folder called orders with th same structure as allocation?
And how should avoid code duplication? For e.g. UOW should be very similar.

from book.

excellent question!

it depends if you're in a microservices environment or in a monolith. we've mostly written the book assuming microservices, so each bounded context is a totally separate application + code repository + deployment.

a monolith is a perfectly valid architectural choice too, and you can absolutely do DDD in a monolith, and yes, folder structure sounds like a good way to make that distinction clear. I don't personally have any direct experience of it, but we're looking to talk about it a bit in the final/epilogue chapter...

from book.

@hjwp
We have been using a monolith architecture with a 3 years project e-commerce. It was entirely developed in Python + AWS Lambda + GraphQL. O coukd point some engineers to talk about the theme.

from book.

i'd be very interested to hear you + your team's reaction to the book - particularly any remaining questions, like this, "how does it work in a monolith" - it will help us write the final chapter...

from book.

done-a-saurus.

from book.