Patterns for Translation Service

Derick,


looking at the abstraction.....always think some thing like this


1. What type of objects returns the system you are building?, are they always similar objects, like English Language, French language,.. here language is a common attribute oke... so we sould think of Factory pattern with language as a abstract class.

2. If you decide to use Factory make sure that Factory class should be singleton always.

2. Does the system you are developing to use accross your company, then don't expose many interfaces to the out side world. so tink of Facad pattern. even with WCF also separate the actual system and service. because must be reuasable with any other application. so should always.

3. Now... the Translation Service may follow a similar steps to carry out the action... so think of template pattern.. bcoz Translation Service is an algorithum....


4. later you may decide to use any third party Translation Service, so make sure that template has adapertors in them so that it is very easy to adapt the uncompatable systems.

The thumb rule is start thinking.... all the palce with all posible patterns. by the time you implement start removing the unwanted (where we don't have extendabilyt or reusability) based on the abstraction..

So open of extension and close for modification :)


Hope this helps.....

Thanks,
Chinna