Get the latest tech news
You're misunderstanding DDD in Angular (and Front end)
Motivation In the recent year or two I've seen lots of discussions around building Domain-Driven Design in Angular applications. My observation is that people discuss things that are orthogonal to DDD at best - or even totally derailed from what DDD is about at its core. Participants who attended my
In other words, which parts of the system should you improve to build competitive advantage: a CRUD-based module for internal employees, or an experimental customer-facing UI? When it comes to monorepos, how you organize your code in directories/repos is purely orthogonal to your business/domain concerns - although it could affect team efficiency ( development and operations- yep, DevOps is NOT about docker or k8s 😅). It's a matter of how much you can or cannot rely on "simple CRUDs"... or how many business processes you've got... or how many people work on the system in parallel, and how much collaboration they need on a daily basis.
Or read this on Hacker News
