redis

pipeline:

 

• pipelining is NOT Redis transactions
• pipelining does not provide atomicity
• pipelining really is nothing more complicated than the fact that Redis server is able to queue up responses in memory
• it is entirely up to the client when to send the requests and when to wait on the responses
• commands in a pipeline must be independent of each other (as individual responses don't get read till the end of the batch)
• sending through too many commands in a single pipeline may cause memory issues and potentially socket timeout, so one may want to flush a pipeline after a number of commands (best to do some performance testing)