Live data from Hacker News

Lessons from a Google App Engine SRE on how to serve over 100B requests per day

cloudplatform.googleblog.com

11–20 of 30 posts

Re: Lessons from a Google App Engine SRE on how to serve over 100B requests per day

#11
post #5
post #4

I used to be a scientist and I went to work at Google to apply their technology to science problems. My first team was SRE- and I have to say, Google's SRE approach to computing completely changed how I thought about things, and more importantly, how I programmed systems that went to production. I've read the SRE book and can highly recommend learning from the principles it lays out.

Can you please give reference to that book ?

[deleted]

Re: Lessons from a Google App Engine SRE on how to serve over 100B requests per day

#12
post #5
post #4

I used to be a scientist and I went to work at Google to apply their technology to science problems. My first team was SRE- and I have to say, Google's SRE approach to computing completely changed how I thought about things, and more importantly, how I programmed systems that went to production. I've read the SRE book and can highly recommend learning from the principles it lays out.

Can you please give reference to that book ?

It's the one mentioned in the interview, http://www.amazon.com/Site-Reliability-Engineering-Productio...

Re: Lessons from a Google App Engine SRE on how to serve over 100B requests per day

#13
post #4

I used to be a scientist and I went to work at Google to apply their technology to science problems. My first team was SRE- and I have to say, Google's SRE approach to computing completely changed how I thought about things, and more importantly, how I programmed systems that went to production. I've read the SRE book and can highly recommend learning from the principles it lays out.

[deleted]

Re: Lessons from a Google App Engine SRE on how to serve over 100B requests per day

#14

I've been seeing a lot of references to SRE recently. Is Google trying to market this position and acquire more engineers? The SRE book, and Google in general, have mentioned that SREs are notoriously hard to hire, and I'm wondering if they are doing a marketing push.

I'd imagine so. Due to SRE becoming such a buzz-word title with many companies doing this so differently, it has increased the difficulty of hiring.

Re: Lessons from a Google App Engine SRE on how to serve over 100B requests per day

#19
post #4

I used to be a scientist and I went to work at Google to apply their technology to science problems. My first team was SRE- and I have to say, Google's SRE approach to computing completely changed how I thought about things, and more importantly, how I programmed systems that went to production. I've read the SRE book and can highly recommend learning from the principles it lays out.

I've skimmed it, but even the appendices alone are worth a look. Not always immediately practical in every situation, as with anything Google, but it's definitely a "handbook" I'll be studying closer over the next few weeks. :)

Oh and while Google Play may be cheaper, it's also on Safari books if folks have subscriptions to that, e.g. via libraries/proquest.

Re: Lessons from a Google App Engine SRE on how to serve over 100B requests per day

#20

I've been seeing a lot of references to SRE recently. Is Google trying to market this position and acquire more engineers? The SRE book, and Google in general, have mentioned that SREs are notoriously hard to hire, and I'm wondering if they are doing a marketing push.

SREs are very hard to hire, speaking from experience. At Google SRE directors and VPs will often cherry-pick promising candidates from the mainline SWE hiring pipeline and give them a "hero call" to convert them to SREs. SREs at Google are also paid more, controlling for level and performance, as a way to hire and retain.

Interesting. Can you expand on "hero call"? What does that entail?
Post reply on HN