Name: DevOpsとSREの違いは？ (What's the Difference Between DevOps and SRE?)
Uploaded: 2021-01-14T07:52:23.000Z
Duration: 5 min 11 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

I'm Liz, a Site Reliability Engineer, or SRE, at Google.

how to build and operate reliable services.

Advocate at Google focused on infrastructure and operations.

And Liz and I are here to settle things once and for all.

But first of all, maybe we should clarify some things.

SETH VARGO: So that's a great question, Liz.

Back in the day, operators and developers

over the metaphorical wall, and operators

were responsible for keeping that code running

Operators had little understanding of the code

bases, and developers had little understanding

But developers were concerned with shipping code,

and operators were concerned with reliability.

LIZ FONG-JONES: So if I understand you correctly,

responsible for features, and the operators

were responsible for stability, meaning the developers wanted

to move faster to get their features out faster

and the operators wanted to move slower to keep things stable?

I could see how that would cause a lot of tension.

So DevOps is a set of practices and a culture designed

to break down those barriers between developers, operators,

we can increase collaboration and thorough put.

And when we introduce humans into the system,

Not only are small, incremental changes easier to review,

but in the event that a gradual change does

Fourth, we need to leverage tooling and automation.

And fifth, we need to measure everything.

Measurement is a critical gauge for success.

And without a way to measure if our first four pillars

were successful, we would have no way of knowing if they were.

So, Liz, you've been an SRE at Google for over 10 years now.

Do you think any of the way that I described DevOps aligns

LIZ FONG-JONES: It's sounding very familiar.

Because, if you think about DevOps as a philosophy,

SRE is a prescriptive way of accomplishing that philosophy.

So if DevOps were an interface in programming language,

you might almost say that SRE is a concrete class that

So, Seth, when you talked about eliminating

organizational silos, what I thought about

is the fact that we share ownership of production

to make sure everyone has the same view and same approach

When you talked about accepting accidents and failure

as normal, what I thought about is the fact that--

we make sure that the failures that happen in our production

systems don't happen the exact same way more than once.

And we accept the failures as normal by encoding

a concept of an error budget of how much the system is allowed

And then third, we talked about making gradual changes.

And when you said that, I thought about the fact

things out to a small percentage of the fleet

And then fourth, when you talked about leveraging

tooling and automation, what I thought about

is the fact that we try to eliminate manual work

and then we try to automate this year's job away.

And then fifth, when you talked about measuring everything,

of measuring the amount of toil that we have

and measuring the reliability and health of our systems.

字幕リスト動画再生

DevOpsとSREの違いは？ (What's the Difference Between DevOps and SRE?)

critical

eliminate

multiple

concept