Sounds good.
One thing I'd like to see is more coverage on Cassandra Internals. Out of
the box Cassandra's great but having a little inside knowledge can be very
useful because it helps you design your applications to work with
Cassandra; rather than having to later make endless optimizations that
could probably have been avoided had you done your implementation slightly

Another thing that may be worth adding would be a recipe that showed an
approach to evaluating Cassandra for your organization/use case. I realize
that's going to vary on a case by case basis but one thing I've noticed is
that some people dive in without really thinking through whether Cassandra
is actually the right fit for what they're doing. It sort of becomes a
hammer for anything that looks like a nail.

On Tue, Jun 26, 2012 at 10:25 PM, Edward Capriolo <>wrote:

> Hello all,
> It has not been very long since the first book was published but
> several things have been added to Cassandra and a few things have
> changed. I am putting together a list of changed content, for example
> features like the old per Column family memtable flush settings versus
> the new system with the global variable.
> My editors have given me the green light to grow the second edition
> from ~200 pages currently up to 300 pages! This gives us the ability
> to add more items/sections to the text.
> Some things were missing from the first edition such as Hector
> support. Nate has offered to help me in this area. Please feel contact
> me with any ideas and suggestions of recipes you would like to see in
> the book. Also get in touch if you want to write a recipe. Several
> people added content to the first edition and it would be great to see
> that type of participation again.
> Thank you,
> Edward

Courtney Robinson
07535691628 (No private #s)

Reply via email to