Why this is in my collection
From the publisher:
A hands-on guide to creating clean web applications with code examples in Java
Highlights
- Domain model at the center, frameworks at the edge — Hombergs's hands-on hexagonal architecture puts the business model in the core and web/persistence behind ports and adapters; the same shape as MDDE's model-versus-platform split — the core is durable, the adapters churn.
- The dependency rule is a rule, and rules can be enforced — all dependencies point inward toward the domain; stated as intention it decays, expressed as automated architecture tests (ArchUnit-style fitness functions) it holds — structure guarded by executable rules instead of code-review vigilance.
- Boundaries cost mapping, and the cost should be chosen consciously — the book is unusually honest about mapping strategies between layers and when to skip them; deliberate, documented shortcuts beat accidental erosion, which is the difference between a design decision and entropy.
- Package structure should express the architecture — organizing code by use case and boundary so the structure is visible in the tree itself; making the model legible in the artifact, the same instinct as folder-per-concept in a knowledge vault.
- Use-case slices over technical layers — cutting the system by what it does for the business rather than by which framework tier the code sits in; behavior-first decomposition, the application-code cousin of modeling business concepts before tables.
Highlights on this page are generated with the help of AI.