Why implementing a Singleton pattern in Java code is (sometimes) considered an anti-pattern in Java world?

by

Testing

One reason is that singletons aren’t easy to handle with unit tests. You can’t control the instantiation and by their very nature may retain state across invocations.

For that reason the principle of dependency injection is popular. Each class is injected (configured) with the classes they need to function (rather than derive via singleton accessors) and so tests can control which dependent class instances to use (and provide mocks if required).

Frameworks such as Spring will control the lifecycle of their objects and often create singletons, but these objects are injected into their dependent objects by the framework. Thus the codebase itself doesn’t treat the objects as singletons.

e.g. rather than this (for example)

public class Portfolio {
   private Calculator calc = Calculator.getCalculator();
}

you would inject the calculator:

public class Portfolio {
   public Portfolio(Calculator c) {
      this.calc = c;
   }
}

Thus the Portfolio object doesn’t know/care about how many instances of the Calculator exist. Tests can inject a dummy Calculator that make testing easy.

Concurrency

By limiting yourself to one instance of an object, the options for threading are limited. Access to the singleton object may have to be guarded (e.g. via synchronisation). If you can maintain multiple instances of those objects, then you can tailor then number of instances to the threads you have running, and increase the concurrent capabilities of your codebase.

More Related Contents:

  1. What is an efficient way to implement a singleton pattern in Java? [closed]
  2. Singletons vs. Application Context in Android?
  3. Why is volatile used in double checked locking
  4. Implementing Singleton with an Enum (in Java)
  5. Double Checked Locking in Singleton
  6. What’s Alternative to Singleton
  7. Singleton Design Pattern: Pitfalls [closed]
  8. Other Ways of Singleton in Java [duplicate]
  9. should a db connection be a singleton?
  10. Java Singleton Pattern
  11. Why use a singleton instead of static methods?
  12. When would the garbage collector erase an instance of an object that uses Singleton pattern?
  13. Singleton pattern (Bill Pugh’s solution)
  14. How to create a singleton class
  15. What are static factory methods?
  16. Real World Example of the Strategy Pattern
  17. Using Singleton design pattern for SQLiteDatabase
  18. Singleton with Arguments in Java
  19. Is there a Java equivalent or methodology for the typedef keyword in C++?
  20. Java JSON serialization – best practice
  21. do we need volatile when implementing singleton using double-check locking
  22. Open Session In View Pattern
  23. Builder Pattern and Inheritance
  24. Is there a recommended way to use the Observer pattern in MVP using GWT?
  25. How thread-safe is enum in java?
  26. Is This Use of the “instanceof” Operator Considered Bad Design?
  27. Why people use message/event buses in their code? [closed]
  28. Law of Demeter with data model objects
  29. Singleton Object in Java Web service
  30. Template design pattern in JDK, could not find a method defining set of methods to be executed in order

Leave a Comment