What are the main disadvantages or limitations of the Service Locator pattern encountered in practice?

Main drawbacks of the Service Locator pattern encountered in practice:

• Hidden dependency: Components obtain dependencies through a global service locator, which makes it difficult to understand what the class depends on and complicates maintenance.

• Testing complexity: Testing classes is more difficult because dependencies are not explicitly passed but retrieved from the locator. Setting up the locator for tests increases coupling and reduces isolation.

• Violation of the Dependency Inversion Principle: Instead of dependencies being injected from outside (Dependency Injection), the class requests them itself, reducing flexibility.

• Global state: Service Locator is often implemented as a singleton, leading to global state and potential issues with thread safety and object lifecycle management.

• Hidden complexity: With a large number of services, the locator becomes a "god object" that knows too much and becomes a bottleneck.

In the end, while Service Locator can simplify initial development, in the long run it complicates maintenance and testing. Explicit dependency injection is often preferable.