−"Let's wrap the external SDK with an Adapter pattern" means fitting an external library's calling conventions to the contract our own code uses.
"A Query Facade works better than a Repository for this query" puts the focus on producing the result a screen needs, rather than on loading and saving business objects. Such names shorten the discussion when the team shares an understanding of the problem and the roles.
Use this page to find a pattern for the problem you are facing. Start with a situation in the selection guide, then follow the individual article to see which roles it separates and why, with examples.
When looking at a pattern, you should think about the following before focusing on its name.
+"Let's wrap the external SDK with an Adapter pattern" means fitting an external library's calling conventions to the contract our own code uses. The contract is just the shape of the call our code expects.
"A Query Facade works better than a Repository for this query" puts the focus on producing the result a screen needs, rather than on loading and saving business objects. A different name draws a different boundary around responsibility. Such names shorten the discussion when the team shares an understanding of the problem and the roles.
This page is a guide to finding the pattern article you need for the problem you are facing. Choose the closest situation in the selection table below, then read the individual article to see, with examples, which roles it separates and why. The names above all started from a concrete annoyance.
Before you pick a pattern name, work out what is actually painful in the code right now. The name comes after that.
