In part one of this series, I introduced the CachedRepository pattern, and demonstrated how it can be applied through the use of simple inheritance to an existing Repository class. This allows us to easily configure whether or not we want to use caching at the repository level through the use of an IOC Container like Structuremap. However, using inheritance to achieve the behavior isn’t always desirable, since generally it’s better to use object composition if possible (this tends to result in more flexible designs).
One benefit of the inheritance-based approach is its simplicity. Both in terms of the code require and in terms of wiring up the interfaces and implementations in the IOC container. You end up with something like this in your StructureMap Initialize() method:
Switching between the two is trivial and the behavior is very clear.
Now, to implement the same strategy using the Strategy Pattern, only a few minor changes are required. First, the CachedRepository class needs to be modified to no longer inherit from EfAlbumRepository, but rather to simply implement IAlbumRepository. Next, it needs to take in an IAlbumRepository in its constructor and assign it to a local instance. Finally, the GetTopSellingAlbums() method needs modified to no longer specify the override keyword, and to call _albumRepository rather than base. The modified version is shown below (the original is in the first CacheRepository article):
With the new class in place, we need to adjust how we configure its use in our IOC container’s initialize method. The code required to avoid the cache remains the same, but the code to set up the correct creation of the CachedRepository object is slightly more involved, as we must now specify the type to provide to the constructor. The result is shown here:
This approach requires some more advanced features from the IOC container. In many systems, access to the IOC container is abstracted away behind a common interface, with simple methods like Register<T> and Resolve<T>, and probably not many overloads for things like specifying constructor parameters. In such setups, the inheritance-based approach will most likely be the simplest one to follow, since it is amenable to this kind of simplistic type resolution. However, if you have access to your IOC container’s more advanced methods, and it supports this kind of resolution specification (as StructureMap does), then the strategy pattern based approach may offer more flexibility.
Thanks to Kyle Malloy on the StructureMap Users mailing list for his assistance with the SM syntax required for this case.