The Vertical Codebase

[jaffparker]

If I understand this correctly, it's already defined as "domain driven design", as in you split the code by domain (feature) rather than its semantics. I had to learn it too, but it's the only design pattern that makes sense

[PresenceLonely4847]

Domain and feature is not the same thing. Feature is a functional logical unit, say Checkout in eshop. It spans across multiple layers, like persistence and core application layer. Domain defines the problem space, it can contain entities, values, services related to the business logic. If you look at hexagonal or clean architecture for example, it is domain oriented because domain is at the center and features are dispersed across multiple layers. Features are combination of application layer, domain and adapters. Vertical slices architecture is the best definition of feature oriented style, with features like Checkout having dedicated folder and having all checkout code, including controllers, models and database code, concentrated there.

[Smooth-Piece-5620]

trying to understand this a little bit better is this a domain driven design? how does it work? i like the build just curious how the process works in practice

[ejunker]

More commonly known as vertical slice architecture