Learning properly about scalability is a hard thing. There is such a diverse amount of text available both online as well as in books that it is difficult to be able to evolve an overall understanding of scalability without having an experienced person to guide you. Or you can buy this book! Not kidding, this is an excellent guide to start learning about scalability. The fact that it has chapters dedicated to programmers as well as managers makes it even better as even a manager who does not have the requisite technical knowledge can go through some of the chapters and understand scalability better. In one single book, you will get all the basic fundamentals required to help you put you on your path to scaling your web architecture for the short, medium and long terms. Written by consultants who help major websites scale, this is the best first book to buy on scalability.
Fantastic book. A must have for any architect, CTO or any one who is in business of building enterprise class scalable websites. Only issue was that pages were jumbled up; so had a little trouble reading.
A good book that should serve as ready reference or guidance for anyone interested in the topic of availability and scaleability. Even though, the guidance/rules that this book mentions, seem simple and seemingly intuitive, in the real-world situations you'll find violating these giving whatever excuse it be. Reading books like this re-affirms our own intuition and awakens you of risks the next time you come across situations that warrants you to apply these rules where appropriate.
The later chapters could have been better explained with examples. For instance, in the chapter on "Avoid or distribute scale", the author could have explained situations where these rules can be applied and where it does not. In the absence situational examples or use-cases, the reader might likely remain confused or worse with false sense of knowledge. The same applies in the chapter on async communication with Message Buseses, where the author talks about cost of data. Some real-world examples/use-cases would really make this book a rich resource for the reader.
All said, this book deserves a place in the book-shelf of a developer, manager, architect or a CTO.