The request
“Create a layered web app package diagram with routes, application services, domain logic, infrastructure adapters, and dependencies.”
Then tryAdd an authentication package.Change EmailAdapter to QueueAdapter.
What is in this drawing
Read the decisions behind it.
01Keep routes thin
Route packages invoke application services.
02Protect domain logic
Business objects remain independent of delivery details.
03Contain adapters
Persistence and email sit in infrastructure.
04Show direction
Dependencies should point inward where possible.
Use to review module boundaries and communication paths in a web application.
More like this
Other examples in this family.
FAQ
Common questions
What is a layered package diagram?
It groups a system by architectural layer and shows how one layer depends on another.
Where do repositories belong?
They are usually infrastructure concerns, even when an interface is referenced by application or domain code.
How detailed should it be?
Show important boundaries and dependencies, not every implementation class.