Graphql Proxy Cache
The graphql-proxy-cache plugin provides the capability to cache responses for GraphQL queries.
The limit-count plugin uses a fixed window algorithm to limit the rate of requests by the number of requests within a given time interval. Requests exceeding the configured quota will be rejected.
The limit-req plugin uses the leaky bucket algorithm to rate limit the number of the requests and allow for throttling.
Graphql Limit Count
The graphql-limit-count plugin uses a fixed window algorithm to limit the rate of GraphQL requests based on the depth of the GraphQL queries or mutations.
The proxy-buffering plugin dynamically disables the NGINX proxy_buffering directive to work with SSE and other upstream services sending stream data.
The traffic-label plugin labels traffic based on user-defined rules and takes actions based on labels and the associated weights for actions.
The traffic-split plugin directs traffic to various upstream services based on conditions and/or weights. It provides a dynamic and flexible approach to implement release strategies and manage traffic.
The OAS Validator plugin validates requests or responses against a defined Open API schema.
The body-transformer plugin transforms the request and/or response body from one format to another, for example, from JSON to XML.
The response-rewrite plugin offers options to rewrite responses that APISIX and its upstream services return to clients.
The soap plugin provides a convenient approach to transform between RESTful HTTP requests and SOAP requests, as well as their corresponding responses.
The proxy-rewrite plugin offers options to rewrite requests that APISIX forwards to upstream services.
The degraphql plugin supports communicating with upstream GraphQL services over regular HTTP requests by mapping GraphQL queries to HTTP endpoints.
The key-auth plugin supports the use of an authentication key as a mechanism for clients to authenticate themselves before accessing upstream resources.
The jwt-auth plugin supports the use of JSON Web Token (JWT) as a mechanism for clients to authenticate themselves before accessing upstream resources.