Proxying traffic beyond plain REST through APISIX: gRPC and gRPC-Web, WebSocket, TCP and UDP stream routes, TLS passthrough, MQTT and Kafka.
Running gRPC APIs behind APISIX: HTTP/2 upstreams, TLS to grpcs backends and the 3.19 verification change, authentication and rate limits for gRPC methods, and choosing between native gRPC, transcoding and gRPC-Web.
Letting browser apps call gRPC services through the grpc-web plugin: content types, CORS defaults, allowed headers, and when an Envoy sidecar or JSON transcoding is the simpler option.
Routing WebSocket connections through APISIX: enabling WebSocket on routes, authentication at upgrade time, long-lived connection limits, metrics labels from 3.19 and load balancing sticky sessions.
Using APISIX as a layer 4 proxy for databases, message brokers and legacy protocols: enabling stream mode, stream routes and matching, PROXY protocol, TLS termination and which plugins work at layer 4.
Routing encrypted traffic by SNI without terminating TLS: tls_passthrough listeners, wildcard SNI matching, mixing passthrough and termination on one port, and the features you give up when the gateway cannot see the payload.
Fronting MQTT brokers with APISIX: the mqtt-proxy plugin on stream routes, MQTT 3.1 and 5.0, client ID hashing to keep sessions on one broker node, TLS for device traffic and scaling broker clusters.
Giving clients controlled access to Kafka through the gateway: Kafka upstreams, SASL/PLAIN with kafka-proxy, WebSocket consumers, authentication and rate limits at the edge, and when native Kafka clients are the better route.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.