That's exactly what i'm doing for my ( almost fulltime) side-project. While we do Microservices at work ( distrubited team and Conway's law does make sense: ht

That's exactly what i'm doing for my ( almost fulltime) side-project. While we do Microservices at work ( distrubited team and Conway's law does make sense: https://ardalis.com/conways-law-ddd-and-microservices/ https://ardalis.com/conways-law-ddd-and-microservices/ ) It doesn't make sense for me personally. So I applied all DDD logic and implemented it in my app. In dotnet there is a useful feature where functionality from referenced projects is included in your main WebApp. Which makes everything pretty clean. I use application logic over 2 "gateways". Where a gateway is a dummy solution that contains Swagger, global things for that project ( eg. auth verification) and uses the controllers/logic from the referenced projects. - SPA - Angular that contains a Ocelot gateway on the same domain ( = no cors issues) - ApiGateway - Contains all the backend api logic and custom integrations with partners. - ShopGateway - Is included in the Frontend. - Frontend - the shop itselve. Currently in the process of making this db-less ( everything over API / messages or using the gateway. The gateway is currently a referenced project ( see up), so everything is pretty fast) In the meantime, i can make "reasonable" quick adjustments and the logic is really flexible. Overview of the solution: https://ibb.co/k5wn07x https://ibb.co/k5wn07x Note: Db migration from "1 project" to this is not complete yet :( . But it's one of the bigger shifts and i'm already 90% finished before i can start the actual shift to MartenDb from EF / Dapper ) If you want a quick summary on the logic behind, DDD would be the answer.