With Early Release ebooks, you get books in their earliest form—the author's raw and unedited content as he or she writes—so you can take advantage of these technologies long before the official release of these titles. You'll also receive updates when significant changes are made, new chapters are available, and the final ebook bundle is released.
As web applications grow, two things begin to happen. They become 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.
You’ll learn about:
Service Oriented Architectures, including services and microservices, for building distributed systems that are more resilient to localized failures
Building systems with failures in mind to help you develop robust designs and systems emerge that reduce brittleness and result in higher availability
Forward-looking risk management for identifying system problems
Scaling your engineering team to build and manage web applications that scale successfully
Monitoring and responsiveness to quickly identify problems when your application begins to act abnormally
Chapter 1What is Availability?
Chapter 2Five Focuses of Availability
Chapter 3Measuring Availability
Chapter 4Improving Your Availability When it Slips
Lee Atchison is the Principal Cloud Architect and Advocate at New Relic. He’s been with New Relic for four years where he led the building of the New Relic infrastructure products, and helped New Relic architect a solid service-based system. He has a specific expertise in building highly available systems.
Lee has 28 years of industry experience, and learned cloud-based, scalable systems during his seven years as a Senior Manager at Amazon.com, where among other things he led the creation of AWS Elastic Beanstalk.
Perhaps the real "meat" will arrive in later chapters? I found the content rather "lightweight". I usually write notes, but had none after reading. Perhaps adequate for a total novice to systems and architecture.
Bottom Line No, I would not recommend this to a friend