Singleton WCF Web Service

The needs of the many, met by one.

In this scenario, we have a look up (WCF) web service that needs to return a matching customer code when invoked with a caller ID parameter. The look up table is static and we want it be responsive.

lookup_table

So it makes sense to keep the table in cache instead of waking up, starting a new session and fetching from the database for every call.

Proactive technologist.

Posted in WCF

What do you think?