Why do we use Interface? Is it only for Standardization? [closed]

by

Purposes of Interfaces

  • create loosely coupled software
  • support design by contract (an implementor must provide the entire interface)
  • allow for pluggable software
  • allow different objects to interact easily
  • hide implementation details of classes from each other
  • facilitate reuse of software

Analogy 1: Much like the US space shuttle, Russian Soyuz spacecraft and Chinese Shenzhou 5 can all dock to the International Space Station, because they implement the same docking interface. (This is just an example – I don’t know if it’s true in real life however let’s suspend our disbelief for the sake of an example)

Analogy 2: Like you can plug various computer monitors into your home computer. You can plug a wall-size TV into it, an old CRT (the thick kind), a 20″ flat screen, or a braille machine for the blind to “see” by touch. There’s compatibility among these various/different devices and your computer because they all agree on interface standards.

Details of C# interfaces —
With C#/OOP interfaces you’re doing the same kind of thing but in the unseen/virtual world.

You’re correct about standardization, but also flexibility, scalability, extensibility, maintainability, reusability, testability and power.

(The more you use software interfaces the more these “buzz words” will be understood. And always consider interfaces in the real world because they have done us equally well.)

More Related Contents:

  1. What does “program to interfaces, not implementations” mean?
  2. Interface vs Abstract Class (general OO)
  3. Interface vs Base class
  4. When to use an interface instead of an abstract class and vice versa?
  5. Constructors vs Factory Methods [closed]
  6. Why would I want to use Interfaces? [closed]
  7. Why can’t I seem to grasp interfaces?
  8. When should one use interfaces?
  9. What is the definition of “interface” in object oriented programming
  10. Difference Between Cohesion and Coupling
  11. When to use mixins and when to use interfaces in Dart?
  12. When to use interfaces or abstract classes? When to use both?
  13. When to implement an interface and when to extend a superclass?
  14. What does ‘low in coupling and high in cohesion’ mean
  15. Why doesn’t Rust support trait object upcasting?
  16. Is there more to an interface than having the correct methods
  17. What is the difference between an abstract method and a virtual method?
  18. What is the rationale behind having companion objects in Scala?
  19. What is the dependency inversion principle and why is it important?
  20. Do write-only properties have practical applications?
  21. Polymorphism – Define In Just Two Sentences [closed]
  22. DDD – the rule that Entities can’t access Repositories directly
  23. Are Polymorphism , Overloading and Overriding similar concepts? [closed]
  24. If-less programming (basically without conditionals) [closed]
  25. Mixin vs inheritance
  26. Does the Single Responsibility Principle work in OOP?
  27. Learning/Implementing Design Patterns (For Newbies) [closed]
  28. In SOLID, what is the distinction between SRP and ISP? (Single Responsibility Principle and Interface Segregation Principle)
  29. When to use a Class in VBA?
  30. Overloading functions

Leave a Comment