I haven't created Redis itself but a Redis client library. It all started with a chat server I wanted to write on top of Boost.Beast (and by consequence Boost.A

I haven't created Redis itself but a Redis client library. It all started with a chat server I wanted to write on top of Boost.Beast (and by consequence Boost.Asio) and at the time none of the clients available would fill my needs and wishes - Be asynchronous and based on Boost.Asio. - Perform automatic command pipelining [1]. All C++ libraries I looked at the time would open new connections for that, which results in unacceptable performance losses. - Parse Redis responses directly in their final data structures avoiding extra copies. This is useful for example to store json strings in Redis and read them back efficiently. With time I built more performance features - Full duplex communication. - Support for RESP3 and server pushes on the same connection that is being used for request/response. - Event demultiplexing: It can server thousands of requests (e.g. websocket sessions) on a single connection to Redis with back pressure. This is important to keep the number of connections to Redis low and avoid latency introduced by countermeasures like [3]. This client was proposed and accepted in Boost (but not yet integrated), interested readers can find links to the review here [2]. [1] https://redis.io/docs/manual/pipelining/ https://redis.io/docs/manual/pipelining/ [2] https://github.com/boostorg/redis/issues/53 https://github.com/boostorg/redis/issues/53 [3] https://github.com/twitter/twemproxy https://github.com/twitter/twemproxy