Autoscaling
Azure Health Data Services provides a managed service for persisting FHIR-compliant healthcare data and interacting with it securely through the API service endpoint.
Autoscaling is a capability to dynamically scale FHIR service based on the load reported. The FHIR service in Azure Health Data Services provides the built-in autoscaling capability and the process is automated. This capability provides elasticity and enables provisioning of more instances for FHIR service customers on demand.
The autoscaling feature for FHIR service is available in all regions where the FHIR service is supported.
Note
Autoscaling feature is subject to the resources availability in Azure regions.
The autoscaling feature adjusts computing resources automatically to optimize service scalability. There's no action required from customers.
Autoscale at Compute level
- Scaling Trigger
Scaling Trigger describes when scaling of the service is performed. Conditions that are defined in the trigger are checked periodically to determine if a service should be scaled or not. All triggers that are currently supported are Average CPU, Max Worker Thread, Average LogWrite, Average data IO.
- Scaling mechanism
The scaling mechanism is applied if the trigger check determines that scaling is necessary. Additionally, the scaling trigger won't be evaluated again until the scaling interval has expired, which is set to one minute for FHIR service.
To ensure the best possible outcome, we recommend customers to gradually increase their request rate to match the expected push rate, rather than pushing all requests at once.
FAQ
What is the cost to enable autoscaling for FHIR service?
The autoscaling feature incurs no extra costs to customers.
What should customers do if there is high volume of HTTP 429 errors?
We recommend customers to gradually increase the request rate to see if brings reduction in HTTP 429 errors. For consistent 429 errors, we ask customer(s) to create a support ticket through Azure portal on issue observed. Support team will engage to understand scaling trigger needs.
Next steps
In this article, you've learned about the FHIR service autoscaling feature in Azure Health Data Services. For more information about the FHIR service supported features, see
FHIR® is a registered trademark of HL7 and is used with the permission of HL7.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for