Strategy Pttern

Strategy Pattern: 

Intent:

The Strategy Pattern is also a behavioral design pattern, but its primary intent is to define a family of interchangeable algorithms, encapsulate each one, and make them interchangeable. It allows the client to choose the appropriate strategy at runtime.

Usage:

It's used when you have a set of related algorithms or behaviors and you want to make these behaviors interchangeable without modifying the client that uses them. This pattern promotes algorithm encapsulation and flexibility.

Components:

In the Strategy Pattern, you typically have 3 main components: 

Context, Strategy, and Concrete Strategies.

Context: Maintains a reference to the selected strategy and uses it to perform its operations.

Strategy: Defines an interface or abstract class that represents the family of algorithms.

Concrete Strategies: Implement the specific algorithms.

Flexibility:

The Strategy Pattern promotes flexibility by allowing you to switch between different algorithms or strategies dynamically at runtime. It's useful when you want to avoid code duplication for similar behaviors with slight variations.