Design pattern that decides implementation depending on the method

by Borja Valdivielso   Last Updated April 15, 2019 11:05 AM

I need to add a new implementation to a 60 method interface, but the client doesn't want to migrate all methods at once. He would like to have both implementations cohabiting, and migrate the methods in packs of 5.

The question is:

Is there any design pattern (creation pattern) that decides in runtime which object instantiates depending on the method we are using. For example:

Thanks a lot.

Best regards,

Borja



Related Questions


What about a design-patterns search engine?

Updated November 08, 2018 03:05 AM


Is Workflow the right approach here?

Updated April 03, 2017 23:05 PM