Comparison
Facade patternvsPass-through method
Facade pattern
you replaced eleven calls across four classes with one method, and callers stopped needing to know the order.
A single simplified entry point over a subsystem of several collaborating classes. Its intent is simplification rather than translation: the facade defines a new, smaller interface where the adapter conforms to an existing one, and it typically wraps many objects where the other wrappers wrap one. It does not hide the subsystem — callers who need the detail can still reach past it, which is the difference between a facade and a boundary.
Full entry →Pass-through method
the service method's whole body is a call to the repository method with the same name and the same arguments.
A method, or a whole layer, that does nothing but forward to the next one down, added because the architecture diagram said there should be a layer there. It is the shallow-module problem at its most literal: interface as wide as the thing it hides, and no complexity absorbed. A layer earns its place by doing something — a transaction, a translation, a policy — and if it does not, deleting it is a genuine improvement.
Full entry →