I was asked to review the book (and received a free electronic copy).
As someone that is very into storage engines, I was quite excited about this. After going over the LevelDB codebase, I would finally get to read a real book about how it works.
I was disappointed, badly.
This book isn’t really about LevelDB. It contains pretty much no background, explanation, history or anything much at all about how leveldb works . Instead, it is pretty much a guide of how to use LevelDB to write iOS applications. There are a lot of chapters dealing with Objective-C, NSString and variants, how to do binding, how to handle drag and drop .
However, things that I would expect, such as explanations of how it works, what does it do, alternative use cases, etc, are very rare, if there at all. Only chapter 10 is really worth reading, and even so, I got the feeling that it only made sense to me because I already knew quite a lot leveldb already. I can’t imagine actually starting from scratch and actually being able to understand LevelDB from this book.
If you are working on iOS apps / OS X, I guess that this might be a good choice, but only if you want to know about actually implementing leveldb. You’ll need to do your actual leveldb learning elsewhere.
The book does contain some interesting tidbits. Chapter 10 is talking about tuning and key policies, and it did have some interesting things to talk about, but it also contain wrong information* (and if I could spot it, with my relatively little experience with LevelDB, I’m pretty sure that there are other things there too that are wrong).
* The book said that is it better to write keys in order, to reduce I/O. But LevelDB writes to a skip list in memory, then flush that entire thing in sorted fashion to disk. Your writes have to be bigger than the buffer size of that to actually matter, and that still won’t help you much.
In short, feel free to skip this book, unless you are very focused on writing LevelDB apps on iOS. In which case it might be a worth it, but I don’t think so. You are better off reading the docs or any of the tutorials.