Building Secure and Reliable Systems: Design, Implementation, and Maintenance from Google SRE was an insightful read.
I found the first half particularly interesting, so I took some notes.
- Security and reliability are emergent properties, not simply implemented features. They emerge from multiple factors in deployment and operations, such as mechanisms, testing, and verification states.
- It's advisable to consider security and reliability from the early stages of a project. As the project progresses, the potential for risk increases, so early consideration is recommended.
- The ease of understanding a system (whether engineers can make accurate inferences) depends on how well complexity is managed (≈ design). Systems that are easy to understand are deeply connected to reliability and security.
I initially thought SRE and security were not closely related, but this book changed my perspective.
Although SRE is not my primary role, I want to read more books related to SRE. In particular, I want to read "Site Reliability Engineering." This book frequently references it, indicating a high level of relevance.
While this book offers valuable insights, I felt that its practical applicability might be limited due to differences in organizational scale and structure.
