Reputation: 1642
I'd like to create a geo-redundant function app, this is what I've done:
WEBSITE_CONTENTSHARE
to point to the same locationThe function is duplicated and works as expected, but should I be doing this?
Upvotes: 4
Views: 2062
Reputation: 13795
Externally you still have two different function app urls, so technically it's not geo-redundant, unless you are managing client app configs for two endpoints, or your function apps are only ever polling resources/operating on a timer.
Further, if the content of your WEBSITE_CONTENTSHARE is corrupted, tampered with or accidentally changed to something incorrect, then both apps will fail.
The typical pattern I have seen for geo-redundancy is to deploy to two resource groups in two separate data centers (this includes splitting the storage accounts - which are cheap assets). This gives true separation and redundancy regardless of use case. You can go one step further for incoming https requests by putting them behind Azure API management. I dug this good post up.
Upvotes: 2