Eagerly awaited, particularly the sections on AI infrastructure.
Stuff that was lacking from the first edition, that it doesn't seem like it will make it into the second edition:
Financial justification and cost optimization, in particular for observability: it's easy to extoll the virtues of collecting metrics, logs, traces, and profiles, but it gets very expensive, very quickly. Conversations about observability quickly throw out the baby with the bath water, rather than laying out clear best practice approaches on when, along the lifecycle of system maturity, additional return on investment can be proven. But FinOps perspectives in general are lacking as well.
Security-focused SRE: rolling out secrets management, permissions management, certificate management, firewall/network management, adapting SIEMs, whether or not traditional SOC work should be integrated with SRE roles and given the same "solve toil like a software engineer" treatment.
I don't know if I'm really suggesting that the book should be twice as long; perhaps there should be multiple volumes: uptime reliability engineering, financial reliability engineering, security reliability engineering, for lack of better phrasing off the top of my head.
I've taken a cursory look at the 1st edition. It looked like an excellent book -- definitely on my 'To Read' list. In fact, I'll put in an order for a copy now.
Eagerly awaited, particularly the sections on AI infrastructure.
Stuff that was lacking from the first edition, that it doesn't seem like it will make it into the second edition:
Financial justification and cost optimization, in particular for observability: it's easy to extoll the virtues of collecting metrics, logs, traces, and profiles, but it gets very expensive, very quickly. Conversations about observability quickly throw out the baby with the bath water, rather than laying out clear best practice approaches on when, along the lifecycle of system maturity, additional return on investment can be proven. But FinOps perspectives in general are lacking as well.
Security-focused SRE: rolling out secrets management, permissions management, certificate management, firewall/network management, adapting SIEMs, whether or not traditional SOC work should be integrated with SRE roles and given the same "solve toil like a software engineer" treatment.
I don't know if I'm really suggesting that the book should be twice as long; perhaps there should be multiple volumes: uptime reliability engineering, financial reliability engineering, security reliability engineering, for lack of better phrasing off the top of my head.
I've taken a cursory look at the 1st edition. It looked like an excellent book -- definitely on my 'To Read' list. In fact, I'll put in an order for a copy now.
FYI the first edition is readable online for free.
https://sre.google/sre-book/table-of-contents/