Layered N Tier
Classic presentation / business-logic / data-access layering within a single deployable — the default shape most CRUD apps start as.
Why we need this / what value this brings
Simple, well-understood separation of concerns (presentation/business/data) that most frameworks already assume.
When to use this
Default for most CRUD-style applications — it's usually already what you're doing without naming it.
How to use or implement this
Keep each layer only talking to the layer directly below it (presentation → business → data), not skipping layers.
Research questions
- Where does this blur with MVC (DesignPatterns/MVC-Hexagonal-Clean) — is layering an architecture pattern or an LLD pattern?
Empty folder — drop notes, links, and findings here as you research.