I'm trying to transform wikipedia examples of strategy pattern to real life problems, but I'm not sure if my scenario does require such pattern.

say we a have a service that gets updates from several clients, and needs to do some processing and move these updates forward, depends on their size.
i would like to keep the service as simple as possible, and open for future updates formats (from other clients) as well.

I thought I could let the updates themselves decide how to be processes and moved forward, by using this pattern, and let the service be a simple as possible. something like this:

```
public class Service {
    void processUpdate(Update myUpdate) {

        myUpdate.process();
        myUpdate.moveForward();
    }
}         

```

Am I wrong ? how (where...) do I assign a strategy to each update ?