Comparisons
Pairs that get conflated in real conversations and in real pull requests — coupling and cohesion, abstraction and indirection, refactoring and rewriting, debt and mess. Neither column wins; what decides is the requirement. Each record leads with the confusion, because the confusion is the reason the record exists.
Encapsulation vs Information hiding
They are used as synonyms, and the result is code that is scrupulously encapsulated and hides nothing. A class with a private field and a public getter and setter for it has encapsulation — the field is private, the access is mediated — and it hides no decision whatsoever, because any caller can put the object into any state. Information hiding is the older and more interesting idea: modules should be decomposed around the decisions most likely to change, and each module should conceal one such decision from all the others. That is a claim about *what* the boundary contains, and it is decided before any keyword is typed. The practical consequence is that the interesting question is never "is this field private" but "what does a caller have to know to use this correctly, and what would break if I changed my mind about the thing behind it". If callers must know the order of operations, the storage format, the units, or that there is a cache, then the decision has leaked no matter how private the fields are. The corollary that people find uncomfortable: a wide interface of private-backed accessors is often worse than a public struct, because it advertises a protection it does not provide.
As the language-level mechanism: private fields, module visibility, a constructor that refuses invalid input, methods that are the only way to change the state.
As the design act that decides *what* to encapsulate: which decision is likely to change, and therefore which knowledge must not escape into callers.
| Dimension | Encapsulation — bundling data with the operations that maintain it, and controlling access | Information hiding — choosing which design decisions the module does not reveal |
|---|---|---|
| Kind of thing | A mechanism the language provides | A design principle about decomposition |
| The question it answers | Who may touch this state, and through what | Which decision must not escape this module |
| Decided when | While writing the class | While deciding what the modules are |
| Can exist without the other | Yes — private fields hiding nothing | Yes — a hidden decision in a language with no access control |
| Test of success | State cannot be changed except through the operations | You can change the hidden decision without editing any caller |
| Classic failure | Getter and setter for every field | Callers depending on ordering, units or storage format |
| Relation to change cost | Indirect — it protects invariants | Direct — it is the thing that bounds how far a change travels |
| Which to reach for first | Second — it implements the decision | First — it is the decision |
The same question, five structures
Layered, hexagonal, clean, vertical slice and modular monolith — compared without naming a winner, and with the block that says where the comparison stops being true.
A tidy table implies an equivalence that does not exist. These are not five points on one axis: layered, hexagonal and clean are statements about dependency direction; vertical slice is a statement about directory grouping; modular monolith is a statement about deployment and module visibility. Most real systems combine several. The where this comparison misleads block on every row is the part worth reading, and it is the reason this page names no winner — none of these is mandatory, and a team that adopts one because a diagram was pretty has skipped the only question that decides it.
These are not five points on one axis. Layered, hexagonal and clean are all statements about *dependency direction*; vertical slice is a statement about *directory grouping*; and modular monolith is a statement about *deployment and module visibility*. You can — and most real systems do — combine several of them: a modular monolith whose modules are vertical slices, each with a hexagonal boundary at its edges. Comparing them as alternatives is the single most common way this table is misread.
The word complexity is doing two jobs here. Layered and vertical slice are cheap to *set up* and can be expensive to *live in* once the codebase is large; clean and hexagonal are expensive up front and their cost is roughly flat afterwards. Any comparison made at week one inverts the ranking you would get at year three, and neither reading is dishonest — they are answering different questions.
Locality is a property of whether the boundaries match the change history, not of the style name. A vertical slice cut along the wrong capability lines has terrible locality, and a layered codebase with only one real feature has perfect locality. The only honest way to compare these columns is to open the last thirty merged changes in your own repository and count the directories each one touched.
Every column here is a claim about *fast tests without infrastructure*, and any of the five achieves that as soon as dependencies are injected rather than constructed — which is a separate decision none of these styles owns. What differs is the default test boundary each one nudges you toward, and that matters more than the theoretical maximum: layered nudges toward class-level tests with mocks, vertical slice toward feature-level tests, and the difference shows up in how much your suite has to change during a refactor.
The columns are answering to different pressures: hexagonal responds to *external* volatility, clean to *domain* richness, vertical slice to *feature count*, and modular monolith to *team count*. A system can score high on one pressure and low on the rest, which is why picking a style from a comparison table rather than from your own pressures is how teams end up with four rings around a CRUD application.
Team fit is not a tiebreaker, it is often the deciding factor, and it is the one this table cannot capture. A structurally superior design that the team will not maintain under deadline degrades into the worst version of itself — half-applied clean architecture, with some code respecting the ring rule and some not, is harder to work in than consistent layering. The right question is which of these your team will still be following in eighteen months.
This row compares familiarity, not intrinsic difficulty, and familiarity is a property of the industry at a moment in time rather than of the design. Layered wins here largely because it is what most people have seen, which is an argument for it and also the reason it is over-applied. It is also worth separating cost-to-read from cost-to-contribute-correctly: vertical slice inverts on those two, and the table's single number hides it.
Ceremony is only waste when the feature did not need it, and every column here is right for some features and wrong for others in the same codebase. That is the actual finding of this row: a uniform ceremony level applied to every feature guarantees you are overpaying on the simple ones or underpaying on the complex ones. Allowing different features to carry different amounts of structure is more valuable than choosing which column to standardise on.
shared/ directory that grows back under a new name, or slices that each reimplement infrastructure slightly differently.Every one of these degradations is the style's own strength taken past the point where it repays — which is why none of them can be called wrong, and why §138 forbids teaching any as mandatory. What makes a codebase bad is not the column it started in but the absence of anyone asking whether the structure still matches the changes arriving. The right comparison to make is between your current structure and your last thirty changes, not between two names on a page.