redis

  • codec
  • Fault injection according to the commands and key
note

This feature requires APISIX to be run on .

It also requires the data sent from clients are well-formed and sane. Therefore, it should only be used in deployments where both the downstream and upstream are trusted.

Like other protocols based on the xRPC framework, the Redis implementation here also has the concept of .

For example, when a Redis client subscribes to channel foo and receives the message bar, then it unsubscribes the channel, there are two requests: subscribe foo and unsubscribe foo.

Fields under an entry of :

Assumed the APISIX is proxying TCP on port , and the Redis is listening on port 6379.

Let’s create a Stream Route:

Once you have configured the stream route, as shown above, you can make a request to it: