What do you think?
Redis Applied Design Patterns
Redis Applied Design Patterns
84 pages, Paperback
First published January 1, 2014
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 2 of 2 reviews
March 11, 2016
Put simply, this could have been a good (great, even) read had it not been so sloppily written.
The book - or should I say the draft since the text resembles a work in progress more than a final product - is lacking on all fronts: roughly a third of the design patterns are a bad fit for Redis (which even the author himself states on a few occasions) or would work well only for smaller data sets; furthermore, the number of any practical considerations of suggested approaches is next to none. The code examples are very few and the writing seems to have been done in haste. Each chapter should have been twice as long, there should have been pros and cons considerations, discussions about memory consumption for different data set sizes, costs of having large sets that don't fit in memory, implementation and maintenance cost of the given approaches compared to the traditional solutions and other not so traditional...
It really is no wonder that Packt had chosen to offer this book for free - had I bought it I would have asked for a refund...
The book - or should I say the draft since the text resembles a work in progress more than a final product - is lacking on all fronts: roughly a third of the design patterns are a bad fit for Redis (which even the author himself states on a few occasions) or would work well only for smaller data sets; furthermore, the number of any practical considerations of suggested approaches is next to none. The code examples are very few and the writing seems to have been done in haste. Each chapter should have been twice as long, there should have been pros and cons considerations, discussions about memory consumption for different data set sizes, costs of having large sets that don't fit in memory, implementation and maintenance cost of the given approaches compared to the traditional solutions and other not so traditional...
It really is no wonder that Packt had chosen to offer this book for free - had I bought it I would have asked for a refund...
November 29, 2014
Please read my longer review at http://cristian.regolo.cc/2014/11/29/...
The first pages of this book briefly introduce the reader to the NoSql way of thinking. Then the author provides a good collection of real-life use cases for Redis: cache management, autosuggest, leaderboards, notifications, real time analysis, and also more complex examples about using Redis as primary in-memory data store (for a commenting systems, an advertising network or your new shiny social network).
The book is short enough that could be read in a day, but such a collection of documented design pattern is good to keep at hand everyday for quick review. The code examples are straightforward to read and understand.
Some of the patterns described here are probably obvious to an intermediate reader. The author just provides very basic examples to start with, covering only the surface of the problems without in-depth discussion.
Regarding the quality of the text, in some cases there are inconsistencies between the examples and the text, and the code uses different variable naming conventions. Different chapters try to explain the same thing without self-reference, and some examples are wrong or outdated.
The first pages of this book briefly introduce the reader to the NoSql way of thinking. Then the author provides a good collection of real-life use cases for Redis: cache management, autosuggest, leaderboards, notifications, real time analysis, and also more complex examples about using Redis as primary in-memory data store (for a commenting systems, an advertising network or your new shiny social network).
The book is short enough that could be read in a day, but such a collection of documented design pattern is good to keep at hand everyday for quick review. The code examples are straightforward to read and understand.
Some of the patterns described here are probably obvious to an intermediate reader. The author just provides very basic examples to start with, covering only the surface of the problems without in-depth discussion.
Regarding the quality of the text, in some cases there are inconsistencies between the examples and the text, and the code uses different variable naming conventions. Different chapters try to explain the same thing without self-reference, and some examples are wrong or outdated.
Displaying 1 - 2 of 2 reviews