data-oriented-architecture

Registry-based polymorphism replaces fragile switch statements by mapping entity types to concrete definitions in a centralized registry, allowing behavior dispatch through lookups. This improves extensibility and maintainability for systems with multiple entity variants.

An extensible plugin architecture avoids deep inheritance by using capability composition with optional capabilities. This pattern maps types to definitions in a registry, allowing you to add isolated behaviors without marker interfaces or complex class hierarchies.

Separate data from behavior by defining a Definition interface and creating a type-to-definition registry. Layered Base, Domain, and Concrete definition interfaces compose behavior while keeping entity data distinct from dispatch logic.

Use context objects in type-dispatch architecture to bundle related parameters together, ensuring stable APIs. Context objects pass required data to registry definitions during lookups, preventing signature changes when new parameters are added.

Registry-based polymorphism supports extending frameworks by adding new entity types without modifying existing switch logic. You map new types to their definitions in the centralized registry, enabling infrastructure-first development for scalable systems.

A centralized registry for type-dispatch requires building infrastructure before domain code, adding initial architectural overhead. It is best suited for systems with multiple similar entity variants rather than simple, static logic with few types.