dependabilityで検索した。
"In other words, I think that if “cloud native” has to be a synonym for anything, it would be “dependability.”"
via Check out this quote from Cloud Native Go - https://learning.oreilly.com/library/view/-/9781492076322/ch06.html
reliabilityよりもdependabilityのほうが硬派で好みだなと思っていたが、この筆者はcloud nativeすなわちdependabilityだと主張している。
"Why are there “site reliability engineers” but no “site dependability engineers”?
There are probably several answers to these questions, but perhaps the most definitive is that the definition of “dependability” is purely qualitative."
via Check out this quote from Cloud Native Go - https://learning.oreilly.com/library/view/-/9781492076322/ch06.html
なぜSDEではなく、SREなのか。おもしろい。
"Interestingly, as illustrated in Figure 6-2, these four categories correspond surprisingly well to the five cloud native attributes that we introduced all the way back in Chapter 1."
via Check out this quote from Cloud Native Go - https://learning.oreilly.com/library/view/-/9781492076322/ch06.html
- Fault prevention
- Fault tolerance
- Fault removal
- Fault forecasting
が、dependabilityを高めるmeansで、
- scalable
- loosely coupled
- resilient
- manageable
- observable
がcloud nativeであると。てか、この本は本当にGoの本なのか？
"As such, many fault prevention techniques come into play during the design and implementation of a service."
via Check out this quote from Cloud Native Go - https://learning.oreilly.com/library/view/-/9781492076322/ch06.html
production engineeringの考え方に、この上流工程への影響を考慮できればいいものになる。
てか、この本が非常に面白いので、cloud native系の本一通り読みたくなる。error budgetの話が出てこないのも好感が持てる。
"There are exactly four ways of finding latent software faults in your code: testing, testing, testing, and bad luck."
via Check out this quote from Cloud Native Go - https://learning.oreilly.com/library/view/-/9781492076322/ch06.html
笑。
"Static analysis is useful for providing early feedback, enforcing consistent practices, and finding common errors and security holes without depending on human knowledge or effort."
via Check out this quote from Cloud Native Go - https://learning.oreilly.com/library/view/-/9781492076322/ch06.html
レビューというと何かと誤解を受けるので、今後はレビューのことを静的解析と呼ぶことにしよう。
"Designing for manageability, first introduced back in “Manageability”, allows a system’s behavior to be adjusted without code changes. A manageable system essentially has “knobs” that allow real-time control to keep your system secure, running smoothly, and compliant with changing requirements."
via Check out this quote from Cloud Native Go - https://learning.oreilly.com/library/view/-/9781492076322/ch06.html
コード変更なしに要求変更に追従できることをmanageabilityというらしい。Goにアイディアをもらうのは良いとして、Javaで実現することはできると思う。
