Dependency Injection & Singleton Design pattern

by

Singletons are like communism: they both sound great on paper, but explode with problems in practice.

The singleton pattern places a disproportionate emphasis on the ease of accessing objects. It completely eschews context by requiring that every consumer use an AppDomain-scoped object, leaving no options for varying implementations. It embeds infrastructure knowledge in your classes (the call to GetInstance()) while adding exactly zero expressive power. It actually lessens your expressive power, because you can’t change the implementation used by one class without changing it for all of them. You simply can’t add one-off pieces of functionality.

Also, when class Foo depends on Logger.GetInstance(), Foo is effectively hiding its dependencies from consumers. This means that you can’t fully understand Foo or use it with confidence unless you read its source and uncover the fact that it depends on Logger. If you don’t have the source, that limits how well you can understand and effectively use the code on which you depend.

The singleton pattern, as implemented with static properties/methods, is little more than a hack around implementing an infrastructure. It limits you in myriad ways while offering no discernible benefit over the alternatives. You can use it however you’d like, but as there are viable alternatives which promote better design, it should never be a recommended practice.

More Related Contents:

  1. What is dependency injection?
  2. Is ServiceLocator an anti-pattern?
  3. In a PHP project, what patterns exist to store, access and organize helper objects? [closed]
  4. How will I know when to create an interface?
  5. What’s the difference between the Dependency Injection and Service Locator patterns?
  6. Can’t combine Factory / DI
  7. Naming Classes – How to avoid calling everything a “Manager”? [closed]
  8. How to explain dependency injection to a 5-year-old? [closed]
  9. Is global constants an anti-pattern?
  10. How do you know when to use design patterns? [closed]
  11. Algorithms vs OOP [closed]
  12. Is there a use-case for singletons with database access in PHP?
  13. Why is Singleton considered an anti-pattern? [duplicate]
  14. Factory Pattern. When to use factory methods?
  15. Why do we need Abstract factory design pattern?
  16. Best practice on PHP singleton classes [duplicate]
  17. How to implement Builder pattern in Kotlin?
  18. Is it possible to create static classes in PHP (like in C#)?
  19. Data Access Layer design patterns
  20. Mediator Vs Observer Object-Oriented Design Patterns
  21. Difference between Bridge pattern and Adapter pattern
  22. Fluent Interfaces – Method Chaining
  23. Using a Strategy and Factory Pattern with Dependency Injection
  24. What is the difference between Builder Design pattern and Factory Design pattern? [closed]
  25. Can’t seem to understand SOLID principles and design patterns [closed]
  26. Factory pattern in C#: How to ensure an object instance can only be created by a factory class?
  27. Are there any viable alternatives to the GOF Singleton Pattern?
  28. How to auto register a class when it’s defined
  29. Monostate vs. Singleton
  30. Auto-register class methods using decorator

Leave a Comment