Does the Azure table storage API cache results?

Question

When I run the same query multiple times against the Azure table storage, is it using caching and speeding up the subsequent queries?

In other words, is it caching the HTTP response?

Answer 1

While I am obviously not privy to the internals:

Azure Storage will issue HTTP 304 based on the ETag headers when you send requests that act upon or return a single entity. Depending on your school of though, that can been seen as formal caching. Outside of that, Azure promotes instant (or more correctly "Optimistic") concurrency, so more aggressive caching would not be prudent. (Cache validation,etc overhead would make optimistic concurrency near impossible).

Outside of the ETag/HTTP exchange, I would assume the intent to be that the developer implement more aggressive caching in the client(s) that are consuming the data/