This is what you need to control yourself, since there is no way to observe the blob or container. However: you can check the eTag container (or blob ) to see if the content has been updated.
As for the survey: every time you do a GET, you get a transaction theft. Not that it was very expensive (half a penny per 100,000 transactions): if you did the survey once a second, you probably spent 15 cents (per instance of the role doing the survey) monthly. However: I think it’s a bit aggressive, especially if you have other actions related to the repository that take place simultaneously (polling queue, etc.).
It comes down to how often you think the blob content will be updated, and how relevant your local cache will be.
, , blob , ( URL- blob). , pub/sub ? , ; .