You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 28, 2023. It is now read-only.
I've got a .NET 6 Azure Function (runtime version 4, consumption plan) where I'm using SnowMaker to generate IDs. I've only got one generator per app domain (singleton dependency injection).
I get IDs as expected, until under heavy load (like requesting 10s or 100s at a time) Azure spins up new instances, in which case sometimes the IDs are unique, and sometimes they're not (IOW, it seems like a function instance sometimes gets the same batch as another instance).
Could I potentially be doing something wrong, or is there some way the Azure functions need to be set up?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've got a .NET 6 Azure Function (runtime version 4, consumption plan) where I'm using SnowMaker to generate IDs. I've only got one generator per app domain (singleton dependency injection).
I get IDs as expected, until under heavy load (like requesting 10s or 100s at a time) Azure spins up new instances, in which case sometimes the IDs are unique, and sometimes they're not (IOW, it seems like a function instance sometimes gets the same batch as another instance).
Could I potentially be doing something wrong, or is there some way the Azure functions need to be set up?
The text was updated successfully, but these errors were encountered: