DesignPatterns
Code-structure and LLD-level patterns — see SYSTEM_DESIGN_ALIGNMENT.md sections 9.9, 9.10, 9.12.
Why we need this / what value this brings
Named patterns give the team shared vocabulary for code structure decisions, and prevent both under- and over-engineering.
When to use this
Reach for a pattern once you've seen the same problem shape at least a couple of times — not preemptively.
How to use or implement this
Learn the pattern's intent (what problem it solves) before applying its textbook structure — a misapplied pattern adds complexity without the benefit.
Subtopics
Empty folder — drop notes, links, and findings here as you research.