As a follow-up on the presentation I did at CloudBrew about Azure Static Web Apps I want to write a series of blog posts.
- Part I - Using the VS Code Extension
- Part II - Using the Astro Static Site Generator
- Part III – Deploying to multiple environments
- Part IV – Password protect your environments
- Part V – Traffic splitting
- Part VI – Authentication using pre-configured providers
- Part VII – Application configuration using staticwebapp.config.json
- Part VIII – API Configuration
- Part IX – Injecting snippets
- Part X – Custom authentication
- Part XI – Authorization
- Part XII - Assign roles through an Azure function
- Part XIII - API integration
- Part XIV – Bring your own API
- Part XV – Pass authentication info to your linked API
- Part XVI(this post) – Distributed Functions
As I mentioned in a previous post, when creating an Azure Static Web App, you get a managed function for free. However where the static part of your Azure Static Web App was globally distributed, the managed functions were deployed to a single region. This of course can have an impact on network latencies when a user is connecting from a region far away.
The good news it that Microsoft recently announced (in preview) Distributed Functions. As the name implies it automatically distributes your Static Web Apps’ managed functions to regions of high demand.
You can activate this feature when creating a new Azure Static Web App:
Or through the APIs section for your existing Azure Static Web App:
Nice!
Remark: Distributed Functions is a feature that is available to the Standard SKU of Azure Static Web Apps