Use the Registry pattern in Java to centralize well-defined lookups without drifting into hidden global wiring or service-location behavior.
Registry centralizes lookup by key. In Java, that can be useful for plugin discovery, serializer tables, strategy catalogs, or other controlled mappings from identifiers to objects or providers. It becomes risky when it expands from a focused lookup table into a hidden application-wide dependency mechanism.
This section treats Registry as a pattern with a narrow sweet spot. The value comes from disciplined lookup and controlled ownership, not from giving every part of the codebase a global place to fetch things.