While working with the library I have come across the following thread:
https://stackoverflow.com/questions/36598183/creating-new-instances-of-cloudtableclient-and-cloudtable-per-transaction?answertab=votes#tab-top
As per the thread, it is recommended that we should remove cloudTable.CreateIfNotExists() call from Table Storage constructor for performance reasons.
I am writing a RESTfull web-service which uses table storage in background. After a long search on web, I could not understand what is the recommended way of handling Table Storage connection. My questions are:
- If I open and close connection in every call, wouldn't it create and overhead?
- If I maintain the connection between calls, then would it be good idea in web environment where multiple users are querying the system simultaneously?
This is more like a query than an issue, but I do not know what is the right place to put it if not here.
While working with the library I have come across the following thread:
https://stackoverflow.com/questions/36598183/creating-new-instances-of-cloudtableclient-and-cloudtable-per-transaction?answertab=votes#tab-top
As per the thread, it is recommended that we should remove
cloudTable.CreateIfNotExists()call from Table Storage constructor for performance reasons.I am writing a RESTfull web-service which uses table storage in background. After a long search on web, I could not understand what is the recommended way of handling Table Storage connection. My questions are:
This is more like a query than an issue, but I do not know what is the right place to put it if not here.