Architecting for Scale: High Availability for Your Growing Applications by Lee Atchison 6 years.

Summer. 5 I read it back in a translation by Peter Publishing House called "Scaling Apps." Growing complex systems” I read it in a couple of days from work. In short, the book is simple, clear and quite short:) Sometimes it seems like the book is too simple.

I cannot help but mention the translation of the book, which is not terrible, but very far from ideal. “Architecting for Scale: High Availability for Your Growing Applications” can be translated as “Scaling Apps” and “Growing Complex Systems.” You can grow potatoes in the country:) And here everything revolves around the correct application architecture, which allows you to scale, while maintaining high availability. If we abstract from the translation and look into the content of the book, the author reveals the following thoughts:

• Availability vs Reliability. It’s not the same thing, but only accessibility is discussed in the book.
• Ways to improve accessibility (Consider failures in design and development, think about scaling, manage risk, control availability, have a problem response plan) Introduction to risk management in the context of IT systems (What is it, the criticality and probability of risk, the risk matrix, risk mitigation, risk mitigation, risk mitigation?) Services and microservices - where were they? 2016 year:) Advantages and disadvantages of services. Discussion of dependencies between services and what it leads to in terms of accessibility
• Application scaling (Two Error Reserve, Service Ownership, Service Classes and Use, SLA, Continuous Improvement)
• Clouds are another hot topic. The author tells about AWS, in the design and creation of which he participated before moving to NewRelic.
• And finally, the conclusion in which the author knocked out the summary under the content of the book

In general, a fairly basic and passbook:)

#Architecture #SoftwareArchitecture #SRE #SystemDesign #DistributedSystems