Architecting For Scale • Lee Atchison & Ken Gavranovic • GOTO 2021 (Category Architecture)
I looked at it. interview Lee Atchison with Ken Gavranovic on the second editionArchitecting For Scale", issued in 2020 year. About my impressions of the first edition I told A year ago. But I was interested in the new edition and the author’s story about it. What did these two respected people discuss? The topics were as follows:
- What problem does “Architecting for Scale” solve? The story of how Lee became an expert in scaling 7 years on Amazon and then on 7 I moved to NewRelic, which also got to the point where they needed to scale. And then Lee wrote the first edition of the book. 2016 year. Then he began to advise various companies on scalability problems and on the basis of this experience he wrote a second edition, expanded and expanded.
- Risk management The author talks about his favorite tool in the form of risk matrices and the ability to use them to communicate with top managers to discuss and prioritize scaling tasks compared to business tasks inside the backlog. I think this is a good and understandable tool.
- Best practices for moving to or starting with microservices Discuss the transition to microservice architecture and how it helps in scalability. Here, the author tells about companies that started such a migration, but stopped in the middle of the process and got an intermediate situation in which everything got worse. The author generalizes this to other large migrations:)
- Project Beanstalk The author recalls with nostalgia AWS Elastic Beanstalk, which he launched at Amazon after the end of the big migration of the web application amazon.com in the first half of the 2000s. The author says that this was the first platform service in AWS that provided a service on top of IaaS for deploiting and scaling web applications.
- Beyond the book: Real-life struggles The author says that during consultations he pays more attention to the processes and procedures within the client companies, and the code and application architecture are the second priority.
- Next step: Operating for scale The author equates scalability with availability. From the point of view of operations, the author focuses on the availability of systems, how deployements, security, and scale testing are arranged. On testing, the author says he values unit tests less and more tests in production. (Chaos Engineering). It also includes game days and production exercises.
- Continuous releases This is about the fundamental role of CI/CD for everything discussed above. In fact, this is a pre-requisite:)
- Future releases The author says that "stay tuned" will continue to be new books:)
#Architecture #SoftwareArchitecture #Software #SoftwareDevelopment #Engineering #SystemDesign #Management #Leadership