This content originally appeared on DEV Community and was authored by Abhinav Pandey
Strategy pattern is a design pattern that allows you to define a family of algorithms, put each of them into a separate class, and make their objects interchangeable.
This is useful when you have a large number of similar algorithms and you want to use them in different ways. It is one of the most common design patterns and is simple to understand and implement.
Strategy pattern is closely related to the Factory pattern - the main difference is that Factory pattern is more useful for deciding the implementation at runtime whereas Strategy pattern is more useful for deciding the implementation while designing the application.
Let's start with some terminology.
- Strategy - A strategy is an interface which defines a family of algorithms.
- Context - A context is an object that uses a strategy to perform an operation.
- Concrete Strategy - A concrete strategy is a class that implements an algorithm.
- Client - A client is a class that tells the Context which strategy to use.
A real world example
Let's think about an example of this in the real world. It is as simple as ordering a pizza.
- We have an oven which can cook a pizza. Consider it a context.
- The pizza is an abstraction. There can be many type of pizzas. So it is a strategy.
- The actual pizza that a customer selects is a concrete strategy.
- When the customer(the client) orders a specific pizza, the contents of the actual pizza are put into the oven, the oven starts to cook and the pizza is ready.
Let's code this up
The Strategy
Let's create a pizza interface.
public interface Pizza {
void prepare();
}
The Concrete Strategy
Let's create multiple concrete strategies.
Our first strategy is a NY Style pizza.
public class NYStyleCheesePizza implements Pizza {
@Override
public void prepare() {
System.out.println("Preparing NY Style Sauce and Cheese Pizza");
}
}
The other is a Pineapple pizza.
public class PineapplePizza implements Pizza {
@Override
public void prepare() {
System.out.println("Preparing Pineapple Pizza even though it is not a real pizza");
}
}
The Context
Let's create a context class for our Oven.
public class Oven {
private Pizza pizza;
public Oven(Pizza pizza) {
this.pizza = pizza;
}
public void bake() {
pizza.prepare();
}
}
The Client
Now, let's create a client class.
public class Client {
public static void main(String[] args) {
Oven oven = new Oven(new NYStyleCheesePizza());
oven.bake();
}
}
Considering the customer orders a NY Style pizza, the oven will start to cook the NY Style pizza.
Advantages of using Strategy Pattern
- Flexible context - You can change the strategy at runtime or even at design time but the context code doesnt have to change.
- Easy to extend - You can add more strategies without having to change the context code.
- Easier to test - You can test the code easily. All you have to do is pass in a mock strategy object to the context.
Strategy pattern is something you might be using already without even knowing it. It is intuitive and easy to understand.
If we talk about modern Java, the most popular occurrence of Strategy pattern is through Spring Qualifiers
Thanks for reading! This should help you understand the concept of strategy pattern. Stay tuned for more design patterns.
If you want to connect with me, you can find me on Twitter @abh1navv
This content originally appeared on DEV Community and was authored by Abhinav Pandey
Abhinav Pandey | Sciencx (2021-12-14T07:55:45+00:00) Pizza flavoured Strategy pattern. Retrieved from https://www.scien.cx/2021/12/14/pizza-flavoured-strategy-pattern/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.