design-patterns solid-principles single-responsibility-principle interface-segregation-principle

Is Interface segregation principle only a substitue for Single responsibility principle?

Is interface segregation principle only a substitue for single responsibility principle ?

I think that if my class fulfill SRP there is no need to extract more than one interface.

So ISP looks like solution in case we have to break SRP for some reason.

Am I right ?

Solution

No. Take the example of a class whose responsibility is persisting data on e.g. the harddrive. Splitting the class into a read- and a write part would not make practical sense. But some clients should only use the class to read data, some clients only to write data, and some to do both. Applying ISP here with three different interfaces would be a nice solution.

Raise Events in .NET on the main UI thread
Mock subscriber of a threaded publisher in Rust
Data Mapper Design Pattern and Gateways
Is it bad practice to make a setter return "this"?
What is Action used in Struts 2 in terms of MVC pattern?
Simplest/cleanest way to implement a singleton in JavaScript
Treating classes as first-class objects
Swift: What other way to store a currentUser than a singleton?
What is dependency injection?
Design pattern for handling a lot of error codes
Is Directory to SubDirectory more of a composition or inheritance?
Is there a typical state machine implementation pattern?
Design pattern for converting one model to another model
Does an additional service class violates Single Responsibility Principle?
Why doesn't more Java code use PipedInputStream / PipedOutputStream?
Regular expression for detecting first name and/or last name
Does Inheritance contradict Dependency Inversion Principle
Why and How to avoid Event Handler memory leaks?
Is Chain of Responsibility pattern just an overkill ? A List of Handlers can accomplish the same
Why would I ever use a Chain of Responsibility over a Decorator?
What's the difference between "Chain of responsibility" and "Strategy" patterns?
Why is the Factory pattern not needed in Haskell? And how are the needs that pattern addresses in OOP addressed in Haskell?
How to implement Decorator pattern in Spring Boot
Is this the Result Pattern / Operation Result Pattern, or something different (if so, what?)
Python class function return super()
ASP.NET MVC Paging for a search form
Is there a common design pattern for making a collection class page-able?
Difference between Strategy pattern and Command pattern
What are worker threads, and what is their role in the reactor pattern?
How to get pagedlist size in android when using paging library with mvvm