💡 What is Interface Segregation Principle (ISP)?
The ISP, part of the SOLID principles, states:
"A client should not be forced to depend on methods it does not use."
When an interface has too many unrelated methods, classes implementing it may end up with unnecessary or unused code, leading to fragile, hard-to-maintain systems.
ISP encourages creating smaller, more specific interfaces to keep things clean and manageable.
🎯 Simple Example
Imagine you’re ordering from a restaurant with a menu full of dishes you don’t like. You have to flip through 30 pages of irrelevant options to find it. Frustrating, right?
What if there were focused, specialized menus — one for sandwiches, one for sushi, one for desserts? Suddenly, ordering becomes becomes easier. This is exactly what ISP suggests:
🚫 No massive, one-size-fits-all interfaces full of unused methods.
✅ Small, specific interfaces tailored to fit the needs of their users.
Code Example
🌟 Benefits
✅ No more unnecessary methods: Each class gets exactly what it needs, nothing more.
✅ Easier to understand, maintain and extend.
✅ Cleaner design: No more empty or "not supported" methods.
⚠️ Signs of Violations
❌ Large Interfaces
❌ Unimplemented Methods
💡 How to Avoid ISP Violations
✅ Refactor Large Interfaces into smaller, more specialized ones.
✅ Implement Only What’s Needed — classes should only implement methods relevant to their behavior.
✅ Focus on Composition, not inheritance, so your code stays flexible and easier to extend without violating ISP.
📰 Others
Interested? 😃 Check out other posts from my programming principles series!
- Liskov Substitution Principle (LSP) Explained in 100 Seconds
- Golang - How a Chef and Waiter Teach the Single Responsibility Principle
- KISS Design Principle Explained in 100 Seconds
- DRY Principle Explained in 100 Seconds
- "Tell, Don't Ask" Principle Explained in 100 Seconds
- Golang Dependency Injection - Just in 5 Minutes!
Follow me to stay updated with my future posts:
Top comments (0)