Proper CloudTableClient instance lifecycle?

Question

I'm using the new WindowsAzure.Storage 2.0 (might not be a revelant information), and I'm implementing data access using CloudTableClient. Most samples I've seen are instanciating a CloudTableClient in the ctor of an ASP MVC Controller (instanciated per web request). Is there any performance penalty doing so? Would it be wise to keep a long running instance in a singleton style?

Answer 1

You need to create a new instance of CloudTableClient with each request. Instance members are not thread-safe, so you can't share a singleton.