Software Architecture with Spring 5.0

The interface segregation principle (ISP)

The principal motivation of the interface segregation principle is aligned with the lean movement where creating values with fewer resources is essential. Here's a short definition for it:

Avoid things that you don't use.

You may have already seen classes (modules) implementing interfaces with some method implementations, such as the following:

public  class Abc implements Xyz { 
  @Override 
  public void doSomething(Param a)   { 
    throw new UnsupportedOperationException 
    ("A good explanation here"); 
  } 
  // Other method implementations 
} 
 

Alternatively, another option called comment as implementation tends to be used, as shown in the following code: 

public  class Abc implements Xyz { @Override public void doSomething(Param ...