This is Lee's highly popular O'Reilly Media book, Architecting for Scale, Second Edition.
As web applications grow, two things begin to happen. They scale to handle significantly more complicated and hence brittle, and they handle significantly larger traffic volume requiring more novel and complicated mechanisms to handle this traffic. This can lead to a death spiral for an application that can lead to brownouts, blackouts, and other quality of service and availability problems.
This book helps you avoid this death spiral by teaching you basic techniques for building applications that can reliably handle huge quantities of traffic, as well as huge variability in traffic without impacting the quality your customers expect.
The second edition of the book is now available! This edition has been updated for 2020. The information has been dramatically updated and reorganized, and new information has been added on cloud computing and serverless computing. I hope you enjoy!
by Ekaterina Novoseltseva, Apiumhub
Architecting for Scale is the first book on their top 30 DevOps books you should read in 2018 list.
“The first one on our DevOps reading list is Architecting for Scale. It is an excellent book to understand real-world paradigms for scaling and managing critical applications. This book covers 5 different elements: availability, risk management, services and microservices, scaling applications and cloud services. This book can be called a practical guide as well, it shows how to prevent an application from becoming slow, inconsistent, or downright unavailable as it grows. Also, in this book the word “Scaling” is explained very well as it is not just about handling more users; it’s also about managing risk and ensuring availability.”
Architecting for Scale is book #3 on their summer reading list.
“Summer is always a good time to catch up on some reading. The days are long and theoretically at least, a bit slower. And like most tech nerds, you'll want to spend that time expanding your IT know-how. Perhaps you want to build more expertise in a certain domain or expand your horizons and learn about a new area. In either case, we've got some books you'll want to check out.
“Most of these tech books are hot off the press. A few have been out for a bit, but haven't lost their sheen and remain highly relevant. Many cover cutting-edge topics that were some of the hottest sessions at Interop Las Vegas this year, including network automation, DevOps, and containers. In fact, some the authors, such as network consultant Jason Edelman and eBay Network Software Engineer Matt Oswalt, were popular speakers at the conference.
“With the rise of cloud and software-defined networking, IT roles are changing so it makes sense for infrastructure pros to get familiar with emerging technologies, hence our book choices. Who knows, perhaps one or more of these books will inspire you to take a different approach in your work, or a whole new path in your IT career.”
What is Single Team Owned Service Architecture (STOSA)? STOSA is an important guiding principle for large organizations that have many development teams that own and manage services comprising one or more applications.
These files are templates for making a risk matrix, as discussed in the chapter “The Risk Matrix”. Please see the book for usage and other information: