Regarding this issue, I would like to explain through an example why we need to understand the RESP
protocol when we write Redis
middleware.
The above code is a very simple TCP
server. We listen to the 8888
port and try to use redis -cli -p 8888
After connecting to the server, then view the printed application layer messages.
We try to execute this code and enter redis-cli -p 8888
to connect.
The server we wrote gets the message from the redis
client:
*1
$7
COMMAND
The above is the content of the RESP
protocol, so if we want to write a Redis
middleware, we need to first understand the RESP
protocol. .
The official website has relevant explanations: https://redis.io/docs/reference/protocol-spec/
RESP
The protocol was originally designed for communication between Redis
servers and clients. The protocol was introduced in Redis 1.2
, and in Redis 2.0
, Become the standard protocol for Redis
communication. This protocol has the following advantages:
Simple implementation
Quick analysis
Directly readable
RESP
According to its protocol prefix, different data types can be serialized, such as integers, strings, arrays, etc., and normal output and error output can also be marked. . In addition to pipelines and publish and subscribe, the RESP
protocol should be the simplest request-response protocol. For more introduction, you can check out the official documentation commented above.
RESP
Different parts of the protocol are separated using \r\n
(line feed character), which supports 5 types of data The types are: simple string, error, integer, complex string and array. Let’s make a table to explain.
Type | Prefix | Remarks | |
---|---|---|---|
Simple string | Simple string starts with | ||
Error data | - | Error data starts with - | |
Integer | : | Integer starts with: | |
$ | Complex string starts with $ | ||
* | Array starts with * |
主机 | 端口 | 密码 | 角色 |
---|---|---|---|
127.0.0.1 | 6379 | 无 | 主库 |
127.0.0.1 | 7380 | 无 | 从库 |
The above is the detailed content of How to implement Redis read and write separation in go. For more information, please follow other related articles on the PHP Chinese website!