Table of Contents

1. Introduction
2. What is the Strategy Pattern?
3. The Strategy Pattern in Object-Oriented Programming
4. Functional Programming: A Quick Overview
5. The Functional Approach to Strategy
6. Callbacks vs. Strategy Pattern: A Comparative Analysis
7. Real-World Examples of the Strategy Pattern in FP
8. Advantages of Using Strategy Pattern in FP
9. Common Pitfalls and How to Avoid Them
10. Strategy Pattern in Popular Functional Languages
11. When to Use Strategy Pattern in FP
12. Wrapping Up

1. Introduction

Software design patterns help developers structure their code in predictable, reusable, and scalable ways. One of the most prominent patterns is the Strategy Pattern, traditionally used in Object-Oriented Programming (OOP). However, modern software development has seen a growing shift toward Functional Programming (FP), and patterns like Strategy are not just applicable but often feel more intuitive in this paradigm.

This article explores how the Strategy Pattern can be applied in Functional Programming. We’ll break it down, understand its core purpose, and look at its application in functional languages and idioms. We’ll also examine how this pattern overlaps with callbacks, which are widely used in FP for handling asynchronous operations and injecting behavior.

By the end, you’ll not only understand how to use the Strategy Pattern in FP but also when and why to apply it, along with best practices and real-world examples.

2. What is the Strategy Pattern?

The Strategy Pattern is a behavioral design pattern that lets you define a family of algorithms, encapsulate each one, and make them interchangeable. The key benefit is that it allows algorithms to vary independently from the clients that use them.

✳️ Key Components:

• Strategy Interface: Defines a common interface for all supported algorithms.
• Concrete Strategies: Implement the strategy interface.
• Context: Uses a strategy object and delegates the work to it.

Imagine an e-commerce system that calculates shipping fees. The strategy could be based on country, weight, or delivery speed. Instead of hardcoding logic into the shipping calculator, you use a strategy to plug in the appropriate behavior.

3. The Strategy Pattern in Object-Oriented Programming

In classic OOP (Java, C#, C++), you define interfaces and classes for strategies.

🔍 Example (Java):

interface PaymentStrategy {
    void pay(int amount);
}

class CreditCardPayment implements PaymentStrategy {
    public void pay(int amount) {
        System.out.println("Paid " + amount + " with credit card.");
    }
}

class PayPalPayment implements PaymentStrategy {
    public void pay(int amount) {
        System.out.println("Paid " + amount + " with PayPal.");
    }
}

class PaymentContext {
    private PaymentStrategy strategy;

    public PaymentContext(PaymentStrategy strategy) {
        this.strategy = strategy;
    }

    public void execute(int amount) {
        strategy.pay(amount);
    }
}

This is classic Strategy Pattern OOP-style—polymorphism using interfaces and classes.

4. Functional Programming: A Quick Overview

Before we apply the Strategy Pattern to FP, let’s review what makes Functional Programming unique:

🔹 Core Concepts:

• First-Class Functions: Functions are treated as values; you can pass them around.
• Higher-Order Functions: Functions that take other functions as arguments or return them.
• Pure Functions: No side effects; output depends only on input.
• Immutability: Data doesn’t change; instead, new data structures are created.
• Declarative Style: Focus on “what” to do, not “how”.

Functional programming languages include Haskell, Scala, Elixir, F#, Clojure, and even JavaScript or Python when used in a functional style.

5. The Functional Approach to Strategy

In Functional Programming, you don’t need interfaces or classes. Instead, you pass functions as arguments, making the code simpler and more expressive.

🧠 The Essence of Strategy in FP:

• Strategy = Function
• Context = Function taking another function

Let’s explore how the Strategy Pattern is naturally implemented in FP.

📌 Example in Python:

def pay_with_credit_card(amount):
    print(f"Paid {amount} with credit card.")

def pay_with_paypal(amount):
    print(f"Paid {amount} with PayPal.")

def execute_payment(amount, strategy):
    strategy(amount)

execute_payment(100, pay_with_credit_card)
execute_payment(150, pay_with_paypal)

That’s it. No classes. No interfaces. Yet the essence of the Strategy Pattern is preserved.

6. Callbacks vs. Strategy Pattern: A Comparative Analysis

🤔 Are Callbacks Just Strategy Pattern in Disguise?

Yes—and no.

Callbacks are often used in:

• Asynchronous operations
• Event handling
• Lazy evaluation

Strategy Pattern, while also using functions, is typically used to:

• Choose behavior dynamically
• Inject logic into reusable components

🔄 Comparison Table:

They are similar in mechanism (passing functions) but different in purpose.

7. Real-World Examples of the Strategy Pattern in FP

🔧 Sorting Algorithms (JavaScript)

const bubbleSort = arr => { /* implementation */ };
const quickSort = arr => { /* implementation */ };

function sortArray(arr, strategy) {
    return strategy(arr);
}

sortArray([3, 2, 1], quickSort);

📦 Logging Strategies (Python)

def log_to_console(message):
    print(message)

def log_to_file(message):
    with open("log.txt", "a") as f:
        f.write(message + "\n")

def logger(message, log_strategy):
    log_strategy(message)

logger("Something happened", log_to_console)

📈 Pricing Algorithms (Go)

type PricingStrategy func(float64) float64

func seasonalDiscount(price float64) float64 {
    return price * 0.9
}

func noDiscount(price float64) float64 {
    return price
}

func calculateFinalPrice(basePrice float64, strategy PricingStrategy) float64 {
    return strategy(basePrice)
}

All these demonstrate flexible, dynamic behavior injected using pure functions.

8. Advantages of Using Strategy Pattern in FP

✅ Cleaner and More Expressive

You avoid boilerplate code like class definitions, getters, setters, etc.

✅ Easily Testable

Each strategy is a pure function—simple to test in isolation.

✅ Promotes Reuse

Strategies can be reused in multiple contexts, making the code more modular.

✅ Encourages Composition

You can compose strategies together to build complex behavior from small functions.

✅ Safer with Immutability

FP languages enforce immutability by default, making the pattern less prone to shared-state bugs.

9. Common Pitfalls and How to Avoid Them

❌ Strategy Leakage

Be careful not to expose implementation details inside strategies. Keep interfaces clean.

❌ Over-Functionalization

Don’t force everything into a strategy—sometimes straightforward logic is just fine.

❌ Unreadable Callbacks

When callbacks get deeply nested (callback hell), refactor using named strategies.

✅ Best Practice:

• Name your strategy functions clearly.
• Use pattern matching where applicable (in languages like Elixir or Haskell).
• Keep your strategies pure.

10. Strategy Pattern in Popular Functional Languages

🔹 JavaScript

JavaScript supports first-class and higher-order functions, making it ideal for Strategy Pattern use.

🔹 Python

Python’s function objects and dynamic typing make it a flexible FP-style environment.

🔹 Haskell

In Haskell, you’d pass functions around and use currying to build strategy chains.

🔹 Scala

Scala, being both OOP and FP, supports strategy through traits or pure functions.

🔹 Elixir

Use anonymous functions (fn) or named modules to implement strategy behaviors.

11. When to Use Strategy Pattern in FP

Use the Strategy Pattern in FP when:

• You have multiple ways to perform an operation.
• You want to inject behavior without hardcoding.
• You want reusable, testable pieces of logic.
• You need to vary logic at runtime (e.g., different pricing models, filtering methods, or validation rules).

Avoid it when:

• The logic is simple and doesn’t need swapping.
• You’re not gaining flexibility or modularity.

12. Wrapping Up

The Strategy Pattern is a powerful concept that translates naturally into Functional Programming. In fact, FP languages often make the pattern easier and more elegant to implement. Instead of verbose class hierarchies, we use functions—simple, composable, and expressive.

Understanding the difference between callbacks and strategies helps in writing clean, maintainable, and testable code. As you grow in your FP journey, mastering such design patterns will help you build robust applications that are easier to reason about and evolve.

Whether you’re working in JavaScript, Python, Haskell, or Scala, embracing the Strategy Pattern the functional way will make your code more powerful and future-proof.

Share on Facebook

Post on X

Follow us

Save