API Gateway 10.15 | Using API Gateway | Implement APIs | Policies | Transport | Enable Bulkhead | Bulkhead feature considerations
 
Bulkhead feature considerations
This section lists the impact of the bulkhead policy on other features that you must remember when using the policy:
Applicable API types
Bulkhead policy is applicable for REST, SOAP, OData, and GraphQL APIs.
However, you can specify the number of maximum concurrent callbacks only for the REST APIs.
Bulkhead limit configuration for APIs in a mashup
API-level bulkhead limit is not applied to the participating APIs. Instead, the bulkhead limit configured at the mashup API-level takes effect.
Bulkhead limit configured for APIs in cluster
In cluster environments, you can specify the bulkhead limit in each node. API Gateway checks the number of concurrent requests per instance and allows or rejects the requests based on the bulkhead limit configured for an API in the corresponding node.
Overall thread pool violation
When you enable the Bulkhead policy and if the overall thread pool is violated, then the requests exceeding the thread pool count are all rejected, and the Connection timeout message is displayed.
Conditional Routing policy
When the Bulkhead policy is enabled with the Conditional Routing policy, then bulkhead limit configured at API-level for the participating APIs is applicable.