Learn Redis the hard way: in production
One problem with Redis is that it looks superficially simple, but actually, like any tool used in critical contexts, there are two possibilities: 1) Know how it works very well and do great things with it. 2) Don't understand it properly and find yourself in big troubles soon or later. Because Redis, in order to provide the good things it provides, has, on one side, a set of limitations, and on the other side is strictly coupled with a number of things related to the operating system, tradeoffs in the configuration and so forth.<p>Certain things I understood over the years that made it better are, of course, improvements in the implementation, but especially things like LATENCY DOCTOR and MEMORY DOCTOR (this one only for versions >= 4.0), that is, most of the things a Redis operations expert can tell you, Redis can tell you directly... without any other help, just observing its internal behavior.<p>There is another aspect. For a long time I believed a Redis book was not really needed. Now I changed my mind, and I see no good enough Redis book out there, and I'm almost planning writing one... I was writing for a long time, incrementally, a C book, that is currently just an incomplete draft. I'm thinking about abandoning for now this project, and start with a Redis book.