Why Strategy pattern in PHP? - Purpose & Use Cases

The Big Idea

What if you could swap complex behaviors like changing gears, without rewriting your whole program?

The Scenario

Imagine you are building a payment system that supports multiple payment methods like credit card, PayPal, and bank transfer. Without a clear plan, you write separate code blocks for each method inside one big function.

The Problem

This manual approach quickly becomes messy and hard to maintain. Every time you add a new payment method, you must change the big function, risking bugs and confusion. It's like trying to fix a tangled ball of yarn.

The Solution

The Strategy pattern helps by letting you define each payment method as its own class with a common interface. Your main code can then switch between these strategies easily without changing its structure, keeping things clean and flexible.

Before vs After

✗ Before

$paymentType = 'paypal';
if ($paymentType == 'credit') {
    // process credit card
} elseif ($paymentType == 'paypal') {
    // process PayPal
} else {
    // process bank transfer
}

✓ After

interface PaymentStrategy {
    public function pay($amount);
}

class PayPalStrategy implements PaymentStrategy {
    public function pay($amount) {
        // process PayPal payment
    }
}

$payment = new PayPalStrategy();
$payment->pay(100);

What It Enables

This pattern enables you to add or change behaviors easily without touching the main code, making your program adaptable and easier to grow.

Real Life Example

Think of a navigation app that can switch between driving, walking, or biking routes. Each mode uses a different strategy to calculate the best path, but the app's main interface stays the same.

Key Takeaways

Manual code mixing different behaviors becomes hard to manage.

Strategy pattern separates behaviors into interchangeable classes.

It makes your code cleaner, flexible, and easier to extend.