The nuts and bolts of implementing synchronous and asynchronous Redis clients supporting pipelining:
In this post I describe different approaches for client-libraries to implement Redis protocol pipelining. I will cover synchronous as well as asynchronous (event-driven) techniques and discuss their respective pros and cons: Synchronous client APIs require the library user to explicitly pipeline commands, potentially yielding optimal protocol performance, but at the cost of additional bookkeeping when handling replies. Asynchronous client libraries, on the other hand, allow automatic pipelining, while being less efficient in their pipelining behavior.
Original title and link: Automatic Async and Sync Pipelining of Redis Commands ( ©myNoSQL)