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
Copy file name to clipboardExpand all lines: articles/api-management/backends.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,8 +91,7 @@ The backend circuit breaker is an implementation of the [circuit breaker pattern
91
91
92
92
> [!NOTE]
93
93
> * Currently, the backend circuit breaker isn't supported in the **Consumption** tier of API Management.
94
-
> * Because of the distributed nature of the API Management architecture, circuit breaker tripping rules are only approximate.
95
-
94
+
> * Because of the distributed nature of the API Management architecture, circuit breaker tripping rules are approximate. Different instances of the gateway do not synchronize and will apply circuit breaker rules based on the information on the same instance.
96
95
97
96
### Example
98
97
@@ -183,7 +182,7 @@ To create a backend pool, set the `type` property of the backend to `pool` and s
183
182
184
183
> [!NOTE]
185
184
> * Currently, you can only include single backends in a backend pool. You can't add a backend of type `pool` to another backend pool.
186
-
> * Because of the distributed nature of the API Management architecture, backend load balancing is approximate.
185
+
> * Because of the distributed nature of the API Management architecture, backend load balancing is approximate. Different instances of the gateway do not synchronize and will load balance based on the information on the same instance.
0 commit comments