As a developer, you are aware of the increasing concern amongst developers and site architects that websites be able to handle the vast number of visitors that flood the Internet on a daily basis. Scalable Internet Architectures addresses these concerns by teaching you both good and bad design methodologies for building new sites and how to scale existing websites to robust, high-availability websites. Primarily example-based, the book discusses major topics in web architectural design, presenting existing solutions and how they work. Technology budget tight? This book will work for you, too, as it introduces new and innovative concepts to solving traditionally expensive problems without a large technology budget. Using open source and proprietary examples, you will be engaged in best practice design methodologies for building new sites, as well as appropriately scaling both growing and shrinking sites. Website development help has arrived in the form of Scalable Internet Architectures .
The concepts mentioned in the book are timeless and still useful but technologies mentioned here are outdated (the book was released at 2006). Worth skimming over but not worth reading
Excellent book. Definitely should be on the bookshelf of anyone running a large web service/site/application. Summary: "performance is not necessarily scalability", "know your tools", "measure", "good logging is really important" and "message buses can be really useful".
The book serves another useful purpose: it is really old school. Code examples are in Perl and C and Unix philosophy (small tools, doing one thing well, connected together) is demonstrated throughout and applied to contemporary technical problems, i.e., building a scalable web application. This is a good antidote the neophilia in technology circles, where only the latest languages, databases, and frameworks are thought worthwhile.
I really did not find this book interesting for the following reasons:
1. Flow of ideas was not clear, I lost context so many times 2. Some ideas are over-illustrated 3. The flow is not smooth 4. Introduced no new ideas, thoughts or eye openers
I might be right, I might be wrong, but I really did not find anything special about this book
What "NoSQL" is to data management, Theo Schlossnagle is to data-center and federated multi-tennant architectures. For good, for bad, for novel insights and resurrected ancient errors ... it's all there, along with a truculent, dismissive attitude.
This book reminds me of a rambling lecture from a professor who probably knows a lot (it's hard to be sure), but isn't very good at helping anyone else learn. I didn't actually finish this book -- switched to Building Scalable Web Sites instead, which seems much better so far.
Remembered why this is 3 stars, easy to read, accessible....mostly, but author goes off on tangents of deeply bewildering programming in the end, so much, I forget the original problem. This also appears to be a book that shills for the Spread daemon... Which is not in itself a bad thing, but do wonder if some solutions could be dealt with message queueing. A decent book still....
This book had just enough material to hold my interest in building scalable web systems. The code formatting in the ebook format was ugly and I just skimmed the last chapter which contains mostly C and perl code but the formatting made it hard to follow the logic. Overall a good starting point on learning about scalable web systems.
This is my first book about scalability. It's was written a decade ago. I'm not sure how relevant the examples are since I'm not working in the field. I give a glimpse on the examples. In general, the book is well organized and the principle is clear. It focuses on the topic: Scalability, and touches relevant topics too.
First half of the book will suit perfectly if you have trouble telling high availability from load balancing. Introduces some of the networking concepts, albeit superficially. The last half of the book is basically an advertisement and a manual for the Spread/Wackamole tools.
Good book but a bit outdated today. Anyone reading it today in 2017 might feel that many concepts explained are too low level given the technologies available today. May be reading a summary of this book will suffice.
While the problems presented in the book are interesting and relevant, the solutions seem a bit dated. I guess more recent books like "Designing Data-intensive applications" and "Scalability Rules" may present more relevant/current solutions.
This book is about principles of building scalable architectures, but the author gives too much attention to a specific technology (Spread) instead of telling about vendor-unspecific approach.