| Product | Status | Details |
|---|---|---|
| NGINX | yes | source |
| Kong | yes | source |
| Envoy | yes | source |
| Tyk | yes | source |
| CA | 3rd party | source 1, source 2, source 3 |
| Azure API Management | yes | To be verified |
| AWS API Gateway | 3rd party | source, possible via AWS CloudFront |
| WSO2 | no | source |
| Tibco Mashery | no | |
| AxWay | no | |
| Software AG | no | |
| Mulesoft | no | |
| 3scale | no | |
| Akana | no | |
| Apigee | no | source |
Last active
March 31, 2020 12:38
-
-
Save zdne/9daf131c0c1c74655e9a0f37db25316e to your computer and use it in GitHub Desktop.
http2 is available in AWS CloudFront, so you could put that in front of AWS API Gateway if you don't need streaming or bidi.
Why having http2 support is so important? Is it because we could have a more fine grained, chattier API?
Hi Z,
This is a great matrix and I like to contribute.
Source for Azure API management support: https://feedback.azure.com/forums/248703/suggestions/34282534
It seems to be supported between the clients and API gateway, but not between the the API gateways and backend yet.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Z, http/2 support is available on the CA API Gateway via a native integration by a CA Partner (Arvata).