“Program to an interface”. What does it mean? [duplicate]

by

To put it simply, instead of writing your classes in a way that says

I depend on this specific class to do my work

you write it in a way that says

I depend on any class that does this stuff to do my work.

The first example represents a class that depends on a specific concrete implementation to do its work. Inherently, that’s not very flexible.

The second example represents a class written to an interface. It doesn’t care what concrete object you use, it just cares that it implements certain behavior. This makes the class much more flexible, as it can be provided with any number of concrete implementations to do its work.

As an example, a particular class may need to perform some logging. If you write the class to depend on a TextFileLogger, the class is forever forced to write out its log records to a text file. If you want to change the behavior of the logging, you must change the class itself. The class is tightly coupled with its logger.

If, however, you write the class to depend on an ILogger interface, and then provide the class with a TextFileLogger, you will have accomplished the same thing, but with the added benefit of being much more flexible. You are able to provide any other type of ILogger at will, without changing the class itself. The class and its logger are now loosely coupled, and your class is much more flexible.

More Related Contents:

  1. Java new keyword
  2. Proper variable initialization and call from another class
  3. What is the cardinality ratio between class and interface? [closed]
  4. What are Generics in Java? [closed]
  5. Why is the clone() method protected in java.lang.Object?
  6. Java : If A extends B and B extends Object, is that multiple inheritance
  7. How should I have explained the difference between an Interface and an Abstract class?
  8. Hiding instance variables of a class
  9. Can we create an object of an interface?
  10. Variable naming conventions in Java
  11. Inner class within Interface
  12. Missing return statement in a non-void method compiles
  13. Overloading in Java and multiple dispatch
  14. Struct like objects in Java
  15. mocking a singleton class
  16. calling setters from a constructor
  17. Java: Static Class?
  18. Is it bad practice to make a setter return “this”?
  19. Multiple classes in single file
  20. Advantage of Local Classes Java
  21. How to do method overloading for null argument?
  22. Is Java 100% object oriented? [closed]
  23. Why are constructors not inherited in java?
  24. Are Java classes objects?
  25. Should methods that throw RuntimeException indicate it in method signature?
  26. Anonymous vs named inner classes? – best practices?
  27. Why are interfaces preferred to abstract classes?
  28. Multiple Inheritance in java
  29. Methods With Same Name as Constructor – Why?
  30. What are the differences between information hiding and encapsulation?

Leave a Comment