Brian from Backblaze here. > Backblaze requires an authorize() call to obtain a token before calling any API function.... this now means 3 calls to upload a fi

Brian from Backblaze here. > Backblaze requires an authorize() call to obtain a token before calling any API function.... this now means 3 calls to upload a file That is correct if you only plan to upload one file. The "authorize" can be reused for weeks, and so can the upload URL. So if you want to upload 100,000 files, it is 100,002 calls to upload the 100,000 files (give or take). It is true this is slightly more complex than it could be, but in turn this means we don't need to have any load balancers in our datacenter (which in turn makes the cost of the service cheaper and at the same time enormously more easily scalable). The idea here is that your application authenticates, then you ask for a URL to a vault that has spare space on it. Then your application "hangs up" (stops talking with that server) and contacts the vault directly. This means there is zero "chatter" between our vaults and that you are talking directly (no hops) to the vault you are storing your data on.