Since a concrete strategy is very often determined at run time based on the provided parameters or so, I would suggest something as follows. @Component public class BurgerStrategy implements MealStrategy { … } @Component public class SausageStrategy implements MealStrategy { … } Then inject all such strategies into a map (with bean name as a … Read more
DI and Strategy work in the same way, but Strategy is used for more fine-grained and short-lived dependencies. When an object is configured with a “fixed” Strategy, for example when the object is constructed, the distinction between Strategy and DI blurs. But in a DI scenario it is more unusual that the dependencies of objects … Read more
The problem with toy examples such as this is that it is often easy to miss the point. In this case, the code could indeed be just implemented as you have shown. In a strategy pattern, the main value is in being able to switch out different implementations for different situations. The example you have … Read more
I think there is some confusion about what the task actually is. In my thinking a task is something that is done by a clerk. So you are able to create a task itself without knowing about a clerk. Based on that task you can choose an appropriate clerk for it. The assignment of the … Read more
The Bridge Pattern makes a distinction between an abstraction and an implementation in such a way that the two can vary independently. I will use the example from Patterns in Java, Volume 1: A Catalog of Reusable Design Patterns Illustrated with UML, Second Edition You need to provide classes that access physical sensors such as … Read more
The strategy pattern is like a 1:many relationship. When there is one type of object and I want to apply multiple operations to it, I use the strategy pattern. For example, if I have a Video class that encapsulates a video clip, I might want to compress it in different ways. So I create a … Read more
Strategy isn’t a magic anti-switch solution. What it does do is give modularise your code so that instead of a big switch and business logic all mixed up in a maintenance nightmare your business logic is isolated and open for extension you have options as for how you create your concrete classes (see Factory patterns … Read more
For me, the link from CKing post and the example in Wikipedia are clear enough, but I’ll try to give you a new example. As they said, Strategy Pattern is mostly a way to change the behaviour of an algorithm at runtime. Of course you can achieve this in many different ways (such as holding … Read more
Let’s explain the strategy pattern the easy way: You have a class Car() with a method run(), so you use it this way in a pseudo language: mycar = new Car() mycar.run() Now, you may want to change the run() behavior on the fly, while the program is executing. For example, you might want to … Read more
The strategy pattern allows you to change the implementation of something used at runtime. The decorator pattern allows you augment (or add to) existing functionality with additional functionality at run time. The key difference is in the change vs augment In one of the questions you linked to it also points out that with the … Read more