service-locator-pattern

Use a lightweight Service Locator pattern to provide a centralized, type-safe registry for resolving service interfaces, reducing direct dependencies without the overhead of full DI containers.

The Service Locator pattern provides a centralized registry for registering and resolving service interfaces at runtime, acting as a simple bridge for cross-cutting concerns like audio, saving, and localization.

You access shared services by defining interfaces, registering concrete implementations in a bootstrapper, and resolving the services by type inside consumer MonoBehaviour methods like Awake().

Use a Service Locator when full DI containers are overkill for your project scale, and you need a lightweight, type-safe bridge to manage cross-cutting concerns without passing direct references through the inspector.

Yes, the Service Locator implementation is type-safe, ensuring that consumers depending on interfaces receive correctly typed concrete implementations when resolving services from the centralized registry.

Passing direct references creates tight coupling to concrete implementations, whereas a Service Locator allows consumers to depend on interfaces resolved at runtime, improving code organization and decoupling game systems.