performance - Handling large object in stateless environment -

we have various windows services load large amount of data i.e. settings, database object used whenever calls made our various .net remoting functions (i know it's old!!). having object containing these settings in memory saves having query database or load data cache whenever queries executed.

settings in "large" object collections of data, id, path, text, etc...

we want move away .net remoting wcf , potentially rid of our windows services , run lot under iis (and azure), being stateless, i'm wondering how should handle this?

1) what's best method can think of? experience preferrably.

one suggestion made me return of client, cache , use relevant settings when making wcf call.

2) numerous services have polling services, monitoring, databases, file locations, ftp locations, etc... how recommend handle in stateless environment?? can't see how handled.

we use sql server, don't want rely heavily on build-in features potentially have suppor likes of mysql & oracle.

thanks.

thierry

you store these settings in appsettings section of config file (web.config iis). using configurationmanager class, can retrieve relevant values needed.

if prefer store static instance of settings object, suggest implementing singleton pattern same. jon skeet's article great starting point.

hope helps.