Brent McCullough

𝗧𝗵𝗲 𝗗𝗼𝗺𝗮𝗶𝗻 𝗹𝗮𝘆𝗲𝗿 𝗳𝗼𝗹𝗱𝗲𝗿 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝘀𝗵𝗼𝘂𝗹𝗱 𝗲𝘅𝗽𝗿𝗲𝘀𝘀 𝗶𝗻𝘁𝗲𝗻𝘁. I didn't understand this a few years ago. The Domain sits at the core of Clean Architecture. It's where you define your entities and the most important business logic. So, I want to share a situation I ran into recently. I was looking at a project I built many years ago. The folder structure in the Domain layer bothered me. I was focusing on technical concerns instead of features. The symptoms of this are folders with names like: - Entities - Enumerations - Exceptions - Repositories - ValueObjects I'm sure you've done (or seen) this at some point. What's the problem with grouping by type? This folder structure doesn't tell you anything about the Domain. So what did I do? I reorganized the folders to group them by "feature". When you do this, domain concepts start appearing in the folder structure. The benefits of this approach are: - Better cohesion - High coupling for a single feature - Low coupling between unrelated features If you ever heard of Vertical Slice Architecture, it's a similar concept. P.S. If you liked this, consider joining The .NET Weekly - my newsletter with 28,000+ engineers that teaches you how to improve at .NET and software architecture. Subscribe here → milanjovanovic.tech What do you think about this approach?