Does Azure storage CreateIfNotExist() result in extra round-trip?
azure, azure-storage
Solution
Yes. It would be better to create the container when you role starts (WebRole.cs/WorkerRole.cs) or when your application starts (Global.asax.cs)
Problem
Most of the examples on working with Azure Storage have `.CreateIfNotExist();` inside the program flow. So if I have a method that puts a blob, but before executing the put it executes `.CreateIfNotExist();`, does this mean that there is an extra round-trip being made to the storage?