Folks, has anyone here done some industrial strength coding against Azure Blob and Table storage? I'm migrating some code that uses local files over to Blobs, as well as some miscellaneous files like user "settings" which are ideal for Tables. By just abstracting the "files" and "settings" a little bit you can get some neat results by changing the backing storage to be Azure.
However, I unpredictably get *(409) Conflict* errors which kill my apps. They usually happen after deleting a container or table and recreating it and writing to it, or after deleting many rows or blobs. I quickly found the MSDN docs do warn you <https://msdn.microsoft.com/library/azure/dd179387.aspx> that some operations can take a while to complete in the background. That makes sense, but has anyone got a good strategy for dealing with this?! I see some people Sleep loop until the 409 goes away, and others use different container or table names when they continue processing. The 1st option is easy but clumsy, the 2nd is superior but you need to rejig your app logic a bit. *Greg K*
