Loading
Topic
Practical software boundaries, dependency direction, domain modeling, modularity, and design-pattern decisions inside applications.
Practice items tagged with Application Architecture.
Selects small structural and behavioral patterns from the problem being solved instead of pattern-name recognition.
Explains inward dependency flow, stable business policy, adapters, and when a smaller project structure is enough.
Applies CQRS proportionally, separating model responsibilities without assuming separate databases, messaging, or event sourcing.
Distinguishes explicit dependency injection from runtime service lookup and identifies the narrow framework boundaries where scoped resolution is legitimate.
Keeps business policy independent from infrastructure while centralizing concrete dependency assembly at the application edge.
Turns a modular-monolith choice into enforceable code and data ownership rather than relying on folders and team discipline alone.