Skip to content

Commit 63ba891

Browse files
committed
edits, syntax
1 parent 169f8f4 commit 63ba891

File tree

1 file changed

+14
-11
lines changed

1 file changed

+14
-11
lines changed

articles/api-management/backends.md

Lines changed: 14 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.custom:
1717

1818
A *backend* (or *API backend*) in API Management is an HTTP service that implements your front-end API and its operations.
1919

20-
When importing certain APIs, API Management configures the API backend automatically. For example, API Management configures the backend when importing:
20+
When importing certain APIs, API Management configures the API backend automatically. For example, API Management configures the backend web service when importing:
2121
* An [OpenAPI specification](import-api-from-oas.md).
2222
* A [SOAP API](import-soap-api.md).
2323
* Azure resources, such as an HTTP-triggered [Azure Function App](import-function-app-as-api.md) or [Logic App](import-logic-app-as-api.md).
@@ -26,7 +26,7 @@ API Management also supports using other Azure resources as an API backend, such
2626
* A [Service Fabric cluster](how-to-configure-service-fabric-backend.md).
2727
* A custom service.
2828

29-
Custom backends require extra configuration, for example, to authorize the credentials of requests to the backend service and define API operations. Configure and manage custom backends in the Azure portal, or using Azure APIs or tools.
29+
API Management supports custom backends so you can manage the backend services of your API. Use custom backends, for example, to authorize the credentials of requests to the backend service. Configure and manage custom backends in the Azure portal, or using Azure APIs or tools.
3030

3131
After creating a backend, you can reference the backend in your APIs. Use the [`set-backend-service`](set-backend-service-policy.md) policy to direct an incoming API request to the custom backend. If you already configured a backend web service for an API, you can use the `set-backend-service` policy to redirect the request to a custom backend instead of the default backend web service configured for that API.
3232

@@ -38,7 +38,6 @@ A custom backend has several benefits, including:
3838
* Easily used by configuring a transformation policy on an existing API.
3939
* Takes advantage of API Management functionality to maintain secrets in Azure Key Vault if [named values](api-management-howto-properties.md) are configured for header or query parameter authentication.
4040

41-
4241
## Circuit breaker property (preview)
4342

4443
Starting in API version 2023-03-01 preview, API Management exposes a [circuit breaker](/rest/api/apimanagement/current-preview/backend/create-or-update?tabs=HTTP#backendcircuitbreaker) property in the backend resource to protect a backend service from being overwhelmed by too many requests.
@@ -47,7 +46,7 @@ Starting in API version 2023-03-01 preview, API Management exposes a [circuit br
4746
* When the circuit breaker trips, API Management stops sending requests to the backend service for a defined time, and returns a 503 Service Unavailable response to the client.
4847
* After the configured trip duration, the circuit resets and traffic resumes to the backend.
4948

50-
The backend circuit breaker is an implementation of the [circuit breaker pattern](/azure/architecture/patterns/circuit-breaker) to allow the backend to recover from overload situations. It augments general [rate-limiting](rate-limit-by-key.md) and [concurrency-limiting](limit-concurrency.md) policies that you can implement to protect the API Management gateway and your backend services.
49+
The backend circuit breaker is an implementation of the [circuit breaker pattern](/azure/architecture/patterns/circuit-breaker) to allow the backend to recover from overload situations. It augments general [rate-limiting](rate-limit-policy.md) and [concurrency-limiting](limit-concurrency-policy.md) policies that you can implement to protect the API Management gateway and your backend services.
5150

5251
### Example
5352

@@ -62,6 +61,8 @@ resource symbolicname 'Microsoft.ApiManagement/service/backends@2023-03-01-previ
6261
name: 'myBackend'
6362
parent: resourceSymbolicName
6463
properties: {
64+
url: 'https://mybackend.com'
65+
protocol: 'http'
6566
circuitBreaker: {
6667
rules: [
6768
{
@@ -74,13 +75,13 @@ resource symbolicname 'Microsoft.ApiManagement/service/backends@2023-03-01-previ
7475
percentage: int
7576
statusCodeRanges: [
7677
{
77-
max: 500
78-
min: 599
78+
min: 500
79+
max: 599
7980
}
8081
]
8182
}
8283
name: 'myBreakerRule'
83-
tripDuration: 'P1H'
84+
tripDuration: 'PT1H'
8485
}
8586
]
8687
}
@@ -99,6 +100,8 @@ Include a JSON snippet similar to the following in your ARM template:
99100
"apiVersion": "2023-03-01-preview",
100101
"name": "myBackend",
101102
"properties": {
103+
"url": "https://mybackend.com",
104+
"protocol": "http",
102105
"circuitBreaker": {
103106
"rules": [
104107
{
@@ -108,16 +111,16 @@ Include a JSON snippet similar to the following in your ARM template:
108111
"interval": "P1D",
109112
"statusCodeRanges": [
110113
{
111-
"max": "500",
112-
"min": "599"
114+
"min": "500",
115+
"max": "599"
113116
}
114117
]
115118
},
116119
"name": "myBreakerRule",
117-
"tripDuration": "P1H"
120+
"tripDuration": "PT1H"
118121
}
119122
]
120-
},
123+
}
121124
}
122125
[...]
123126
}

0 commit comments

Comments
 (0)