4 — Event-Driven Design
Purpose
[stub: event-driven-design]
Metadata
| Author | Amit Singh |
| Scope | low-level-design |
Local graph
Related notes
1 — Hexagonal Architecture
Isolates core domain logic behind ports and adapters so infrastructure choices like databases or messaging can be swapped without touching business rules.
2 — Clean Architecture
Layers a system into entities, use cases, interface adapters, and frameworks so dependencies always point inward toward stable business rules.
3 — Domain-Driven Design Essentials
Introduces bounded contexts, aggregates, and ubiquitous language as the core tools for modeling complex business domains in code.
5 — CQRS Basics
Splits read and write models into separate paths so each can be optimized and scaled independently instead of sharing one general-purpose model.