Skip to content

Commit f22b33c

Browse files
authored
Update fhir-service-autoscale.md
1 parent 4e678bc commit f22b33c

File tree

1 file changed

+23
-5
lines changed

1 file changed

+23
-5
lines changed

articles/healthcare-apis/fhir/fhir-service-autoscale.md

Lines changed: 23 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,20 +9,38 @@ ms.date: 06/06/2022
99
ms.author: kesheth
1010
---
1111

12-
# FHIR service autoscale
12+
# Autoscaling
13+
## Overview
1314

14-
FHIR service in Azure Health Data Services is a managed service allowing customers to persist FHIR-compliant healthcare data and interact with it securely through the API service endpoint. The FHIR service provides the built-in autoscale capability to meet various workloads.
15+
FHIR service in Azure Health Data Services is a managed service allowing customers to persist FHIR-compliant healthcare data and interact with it securely through the API service endpoint.
1516

16-
## What is FHIR service autoscale?
17+
Auto scaling is a capability to dynamically scale your FHIR service based on the load reported. Auto scaling gives great elasticity and enables provisioning of additional instances for your FHIR service on demand. FHIR service in Azure Health data services provides the built-in autoscale capability and the entire auto scaling process is automated.
1718

18-
The autoscale feature for FHIR service is designed to provide optimized service scalability automatically to meet customer demands when they perform data transactions in consistent or various workloads at any time. It's available in all regions where the FHIR service is supported. Keep in mind that the autoscale feature is subject to the resources available in Azure regions.
19+
The autoscale feature for FHIR service is designed to provide optimized service scalability automatically to meet customer demands when they perform data transactions in consistent or various workloads at any time. It's available in all regions where the FHIR service is supported.
1920

20-
## How does FHIR service autoscale work?
21+
>[!Note] Autoscale feature is subject to the resources availablitity in Azure regions.
22+
23+
## Description
2124

2225
The autoscale feature adjusts computing resources automatically to optimize the overall service scalability. It requires no action from customers.
2326

2427
When transaction workloads are high, the autoscale feature increases computing resources automatically. When transaction workloads are low, it decreases computing resources accordingly. Whether you're performing read requests that include simple queries like getting patient information using a patient ID, and advanced queries like getting all DiagnosticReport resources for patients whose name is "Sarah", or you're creating or updating FHIR resources, the autoscale feature manages the dynamics and complexity of resource allocation to ensure high scalability.
2528

29+
Auto scaling policies defined for FHIR service consists of two parts
30+
31+
* Scaling Trigger
32+
33+
Scaling Trigger describes when scaling of the service will be 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.
34+
35+
* Scaling mechanism
36+
37+
Scaling Mechanism describes how scaling will be performed when it is triggered. Mechanism is only applied when the conditions from the trigger are met.
38+
There are three factors that determine when the service will be scaled:
39+
1. Lower load threshold is a value that determines when the service will be scaled in. If the average load of all instances is lower than 20% of CPU usage then the service will be scaled in.
40+
1. Upper load threshold is a value that determines when the service will be scaled out. If the average load of all instances is higher than 70% of CPU usage then the service will be scaled out.
41+
1. Scaling interval is used determines how often the trigger will be checked. Once the trigger is checked, if scaling is needed the mechanism will be applied. If scaling is not needed, then no action will be taken. In both cases, trigger will not be checked again before scaling interval expires again. Scaling interval is set ot 1 minute.
42+
43+
## FAQ
2644
### What is the cost of the FHIR service autoscale?
2745

2846
The autoscale feature incurs no extra costs to customers based on the new API billing model.

0 commit comments

Comments
 (0)