That's the older edition of the book which covered Redis, Neo4J, CouchDB, MongoDB, HBase, Riak and Postgres. At the time this was published I was already using CouchDB, Redis and PostgreSQL so we bought a (small) crate of these for my new department's employees.
The new edition can be found at https://amzn.to/2KpxOqU and covers Redis, Neo4J, CouchDB, MongoDB, HBase, Postgres, and DynamoDB. I think the most interesting thing about the new edition is that it drops Riak in favor of DynamoDB. They're both K/V stores but trading an open source database for a DBaaS shows me how entrenched the Amazon ecosystem has become in the last 5 years.
Interestingly, one of the authors answers the question of how they chose which databases to cover with "We did have some criteria, if not explicit. The databases had to be open source—we didn’t want to cover any databases that would tie readers to a company." I guess that's not a strong part of the criteria? I guess a database experimenter could still complete the book's exercises using Amazon's free tier?
second edition editing seemed pretty laser focused on the chapter changes, with specific editors focused on specific databases whereas first edition seemed a bit more cohesive with editors focused on the book as a whole.
The CMU Database Group and Andy Pavlo are great. They have some great courses on their YouTube channel [1], anything you might ever want to know about databases.
Such as their series on hardware accelerated databases [2] (Kinetica, MapD, SQream DB, BlazingDB, Brytlyt, Swarm64)
Challenges encountered when building systems, and the resulting lessons learned, rarely become obsolete. The specific product that resulted from the efforts may fade, but the knowledge abstracted from the efforts does not.
I read the HN comments before clicking through the link. I had assumed it covered more "classical" databases, like SQLite. But your comment makes a little more sense given the specific databases covered. Though I say that out of ignorance -- e.g. I don't know for sure what makes NuoDB a "fundamentally new architecture".
