What is the need for providing different implementations of the same interface?

The need to provide different implementations of the same interface is related to the principles of polymorphism and flexibility in programming. The main reasons:

• Different behaviors under one contract: An interface defines a set of methods, and different classes can implement them differently, allowing the same code to be used with different implementations.

• Simplification of testing: Real implementations can be replaced with stubs or mocks that implement the same interface.

• Extensibility and maintainability: Adding new implementations does not require changing existing code that works with the interface.

• Dependency inversion: It allows depending on abstractions rather than concrete classes.

Example:

interface PaymentProcessor {
    void processPayment(double amount);
}

class CreditCardProcessor implements PaymentProcessor {
    public void processPayment(double amount) {
        // processing credit card payment
    }
}

class PayPalProcessor implements PaymentProcessor {
    public void processPayment(double amount) {
        // processing PayPal payment
    }
}

// Client code works with the interface without knowing the specific implementation
void checkout(PaymentProcessor processor, double amount) {
    processor.processPayment(amount);
}