接口隔離原則(ISP)要求不強制客戶端依賴未使用的接口。其核心是用多個小而精的接口替代大而全的接口。違反該原則的表現(xiàn)包括:類實現(xiàn)接口時拋出未實現(xiàn)異常、存在大量無效方法實現(xiàn)、無關(guān)功能被強行歸入同一接口。應(yīng)用方法包括:按常用方法組劃分接口、依據(jù)客戶端使用拆分接口、必要時使用組合替代多接口實現(xiàn)。例如將包含打印、掃描、傳真方法的Machine接口拆分為Printer、Scanner和FaxMachine。在小型項目或所有客戶端均使用全部方法時可適當(dāng)放寬規(guī)則。
The Interface Segregation Principle (ISP) is one of the five SOLID principles of object-oriented design. Simply put, it states that clients should not be forced to depend on interfaces they don’t use. In practical terms, this means it’s better to have many smaller, specific interfaces rather than one large, general-purpose interface.
Why It Matters in Real-World Code
Think of a scenario where you have a class that implements an interface with ten methods, but your class only needs three of them. If you're forced to implement all ten, you end up writing empty or throwaway implementations for the rest — which clutters your code and makes maintenance harder.
This principle helps reduce side effects from changes, keeps dependencies clean, and improves maintainability by ensuring classes only interact with what they need.
Signs You’re Violating ISP
Here are some common symptoms of violating the Interface Segregation Principle:
- Your class implements an interface but throws
NotImplementedException
for some methods. - You see a lot of “dummy” method implementations just to satisfy an interface.
- Multiple unrelated features are grouped into one interface, forcing clients to deal with unnecessary dependencies.
If any of these sound familiar, it might be time to break that big interface into smaller, more focused ones.
How to Apply ISP Effectively
Applying ISP doesn’t mean creating a new interface for every single method — that would overcomplicate things. Instead, focus on grouping related behaviors logically. Here’s how:
- Identify groups of methods in a large interface that are commonly used together.
- Split the interface based on client usage — if two clients use different parts, split them into two interfaces.
- Use composition when needed — instead of one class implementing multiple interfaces, consider combining smaller services.
For example, instead of having one Machine
interface with print()
, scan()
, and fax()
, create separate Printer
, Scanner
, and FaxMachine
interfaces. That way, a basic printer doesn’t have to pretend it can fax.
When It’s Okay to Bend the Rules
Like most design principles, ISP isn’t absolute. Sometimes merging interfaces makes sense for simplicity or performance reasons — especially in small projects or prototypes where over-engineering adds overhead. Also, if all clients truly do use all the methods, there’s no harm keeping a larger interface.
But as a rule of thumb: if you notice certain methods being ignored or faked in implementations, it’s a good time to revisit your interface design.
Basically, that's the idea behind ISP — keep interfaces lean, relevant, and respectful of the classes that use them.
The above is the detailed content of What is the interface segregation principle?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Java supports asynchronous programming including the use of CompletableFuture, responsive streams (such as ProjectReactor), and virtual threads in Java19. 1.CompletableFuture improves code readability and maintenance through chain calls, and supports task orchestration and exception handling; 2. ProjectReactor provides Mono and Flux types to implement responsive programming, with backpressure mechanism and rich operators; 3. Virtual threads reduce concurrency costs, are suitable for I/O-intensive tasks, and are lighter and easier to expand than traditional platform threads. Each method has applicable scenarios, and appropriate tools should be selected according to your needs and mixed models should be avoided to maintain simplicity

In Java, enums are suitable for representing fixed constant sets. Best practices include: 1. Use enum to represent fixed state or options to improve type safety and readability; 2. Add properties and methods to enums to enhance flexibility, such as defining fields, constructors, helper methods, etc.; 3. Use EnumMap and EnumSet to improve performance and type safety because they are more efficient based on arrays; 4. Avoid abuse of enums, such as dynamic values, frequent changes or complex logic scenarios, which should be replaced by other methods. Correct use of enum can improve code quality and reduce errors, but you need to pay attention to its applicable boundaries.

JavaNIO is a new IOAPI introduced by Java 1.4. 1) is aimed at buffers and channels, 2) contains Buffer, Channel and Selector core components, 3) supports non-blocking mode, and 4) handles concurrent connections more efficiently than traditional IO. Its advantages are reflected in: 1) Non-blocking IO reduces thread overhead, 2) Buffer improves data transmission efficiency, 3) Selector realizes multiplexing, and 4) Memory mapping speeds up file reading and writing. Note when using: 1) The flip/clear operation of the Buffer is easy to be confused, 2) Incomplete data needs to be processed manually without blocking, 3) Selector registration must be canceled in time, 4) NIO is not suitable for all scenarios.

HashMap implements key-value pair storage through hash tables in Java, and its core lies in quickly positioning data locations. 1. First use the hashCode() method of the key to generate a hash value and convert it into an array index through bit operations; 2. Different objects may generate the same hash value, resulting in conflicts. At this time, the node is mounted in the form of a linked list. After JDK8, the linked list is too long (default length 8) and it will be converted to a red and black tree to improve efficiency; 3. When using a custom class as a key, the equals() and hashCode() methods must be rewritten; 4. HashMap dynamically expands capacity. When the number of elements exceeds the capacity and multiplies by the load factor (default 0.75), expand and rehash; 5. HashMap is not thread-safe, and Concu should be used in multithreaded

Java enumerations not only represent constants, but can also encapsulate behavior, carry data, and implement interfaces. 1. Enumeration is a class used to define fixed instances, such as week and state, which is safer than strings or integers; 2. It can carry data and methods, such as passing values ??through constructors and providing access methods; 3. It can use switch to handle different logics, with clear structure; 4. It can implement interfaces or abstract methods to make differentiated behaviors of different enumeration values; 5. Pay attention to avoid abuse, hard-code comparison, dependence on ordinal values, and reasonably naming and serialization.

Singleton design pattern in Java ensures that a class has only one instance and provides a global access point through private constructors and static methods, which is suitable for controlling access to shared resources. Implementation methods include: 1. Lazy loading, that is, the instance is created only when the first request is requested, which is suitable for situations where resource consumption is high and not necessarily required; 2. Thread-safe processing, ensuring that only one instance is created in a multi-threaded environment through synchronization methods or double check locking, and reducing performance impact; 3. Hungry loading, which directly initializes the instance during class loading, is suitable for lightweight objects or scenarios that can be initialized in advance; 4. Enumeration implementation, using Java enumeration to naturally support serialization, thread safety and prevent reflective attacks, is a recommended concise and reliable method. Different implementation methods can be selected according to specific needs

Optional can clearly express intentions and reduce code noise for null judgments. 1. Optional.ofNullable is a common way to deal with null objects. For example, when taking values ??from maps, orElse can be used to provide default values, so that the logic is clearer and concise; 2. Use chain calls maps to achieve nested values ??to safely avoid NPE, and automatically terminate if any link is null and return the default value; 3. Filter can be used for conditional filtering, and subsequent operations will continue to be performed only if the conditions are met, otherwise it will jump directly to orElse, which is suitable for lightweight business judgment; 4. It is not recommended to overuse Optional, such as basic types or simple logic, which will increase complexity, and some scenarios will directly return to nu.

The core workaround for encountering java.io.NotSerializableException is to ensure that all classes that need to be serialized implement the Serializable interface and check the serialization support of nested objects. 1. Add implementsSerializable to the main class; 2. Ensure that the corresponding classes of custom fields in the class also implement Serializable; 3. Use transient to mark fields that do not need to be serialized; 4. Check the non-serialized types in collections or nested objects; 5. Check which class does not implement the interface; 6. Consider replacement design for classes that cannot be modified, such as saving key data or using serializable intermediate structures; 7. Consider modifying
