Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
20250709_What is SRE, and Why Are We Here Toget...
Search
gonkun
July 27, 2025
Technology
66
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
20250709_What is SRE, and Why Are We Here Together?
gonkun
July 27, 2025
More Decks by gonkun
See All by gonkun
20250424_Reliable Communication Through Diagrams
gonkun
0
38
20240119_KEDAでスパイク負荷を迎え撃つ。メトリクスとスケジュールドリブンなオートスケールでKubernetes上のプロダクトの信頼性を高めよう/lets_use_keda_for_reliability
gonkun
1
440
20230929_SRE_NEXT_エラーバジェット運用までの取り組み-信頼性の低下に対するアクションを定義しよう / Let's define actions against unreliability
gonkun
2
3.8k
はじめの一歩を踏み出したい方へ~SREというロールを担うためにやったこと、学びや反省 / Let's start the first step to the SRE
gonkun
2
670
Other Decks in Technology
See All in Technology
JSONataとAWS Step Functionsで目指すRuntimelessな世界
mu7889yoon
1
490
なぜ「決定性」が 決定的に重要なのか? Durable Execution 基盤の数理的理解 #serverlessjp / ServerlessDays Tokyo 2026
ytaka23
4
1.3k
高負荷プロダクション環境におけるAWS Lambdaのリアル 〜スケールとコストを左右する実行ライフサイクルの技術仕様〜
maimyyym
2
550
AIに書かせて、プラットフォームで縛る ― EKSプラットフォームで実践した責任境界と権限設計
elmodev09
0
420
SREへの勘違いに気づいた後の話
tomodakengo
0
150
GoのInterface内部構造から学ぶ!最高パフォーマンスを出すコード設計
yappli_developers
1
290
CI/CDではもう遅い - 人とAIが迂回しないDevSecOps Verify基盤の再設計 -
kintotechdev
0
160
AIエージェントの一手は 誰も見ていない - Falco拡張OSS「Prempti」とeBPFで サーバーレス実行基盤を二層防御する
keitah
1
570
人間はどの意思決定を手放せるのか
kawasima
16
8.2k
Claude Codeを「使うほど育つ」AI秘書にするノウハウ
minorun365
PRO
33
32k
リアーキテクチャ後の障害ゼロを目指したShadow Testingの取り組み
nihonbuson
PRO
1
180
What the customer really needed
kawaguti
PRO
3
220
Featured
See All Featured
Claude Code のすすめ
schroneko
67
230k
More Than Pixels: Becoming A User Experience Designer
marktimemedia
3
530
Visual Storytelling: How to be a Superhuman Communicator
reverentgeek
2
670
Testing 201, or: Great Expectations
jmmastey
46
8.3k
Writing Fast Ruby
sferik
630
63k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
31
10k
How to Talk to Developers About Accessibility
jct
2
550
Reflections from 52 weeks, 52 projects
jeffersonlam
356
21k
Redefining SEO in the New Era of Traffic Generation
szymonslowik
1
430
HTML-Aware ERB: The Path to Reactive Rendering @ RubyCon 2026, Rimini, Italy
marcoroth
5
740
Git: the NoSQL Database
bkeepers
PRO
432
67k
The AI Revolution Will Not Be Monopolized: How open-source beats economies of scale, even for LLMs
inesmontani
PRO
3
3.7k
Transcript
What is SRE, and Why Are We Here Together? Sasaki
Yuta
What is The Goal of our SRE?
To Make our SRE Unnecessary What is The Goal of
our SRE?
Build a Culture Where Engineers Themselves Deliver & Maintain User
Value Reliability To Make our SRE Unnecessary
Why Do We Need SRE?
To Maximize Both Speed and Reliability Why Do We Need
SRE?
When are Incidents Most Likely to Occur?
When Changes are Deployed to Production
Should we freeze releases to stay safe?
Should we freeze releases to stay safe? No…
Stability Delivery User Satisfaction
Stability Delivery User Satisfaction
Stability Delivery User Satisfaction Stability vs. Delivery: Finding the Sweet
Spot
Google advocated SRE Changing Fast and Safely Google's Answer in
2003
Changing Fast and Safely SRE: A Set of Practices to
Balance Development and Reliability SRE Practices
SRE Is a Practice, Not a Title Changing Fast and
Safely SRE Practices SRE as a Title
Everyone can Behave as a SRE Changing Fast and Safely
Behave Engineers SRE Practices
Changing Fast and Safely Behave Engineers Spreading cultures ↓ SREs
SRE Practices
To Make our SRE Unnecessary What is The Goal of
our SRE?
Build a Culture Where Engineers Themselves Deliver & Maintain User
Value Reliability To Make our SRE Unnecessary
Why We Believe This?
Why We Believe This? It’s the Fastest Way to Deliver
Value
“SRE should only take on work that SRE can perform
significantly more efficiently than anyone else.”
Another Background: The Bottleneck Risk ・・・ SREs fast-growing product teams
& Products
Another Background: The Bottleneck Risk ・・・ Requests SREs Bottleneck fast-growing
product teams & Products
Fast Alone, Better Together ・・・ SREs Requests Requests Collaboration Requests
Requests fast-growing product teams & Products
Empowering Product Teams to Practice SRE - Safely ・・・ SREs
Provide Support and Guardrails Requests Requests fast-growing product teams & Products
One Ask: Keep Long-Run Speed in Mind ・・・ SREs fast-growing
HRS teams & Products Requests ? ? ? ? ? ? Which will be the fastest? Requests
Fast Execution, Maximum User Value ・・・ SREs Choose the Fastest
Way fast-growing product teams & Products
SREs Provides Guardrails, Knowledge & Permissions for Safe Self-Service ・・・
SREs Requests Provide Support and Guardrails fast-growing product teams & Products
SREs Provides Guardrails, Knowledge & Permissions for Safe Self-Service ・・・
SREs Requests Provide Support and Guardrails fast-growing product teams & Products Reach Out Anytime — Your Candid Thoughts Keep us Fast
Shared Mindset Elevates SRE Maturity 32 1 3 Able to
implement SRE practices alongside SREs The team can carry out SRE practices without SRE support 2 0 No SRE practices implemented With support from SRE, the team can carry out SRE practices
Everyone can Behave as a SRE
In the end, we would say, "We're all SREs."
Our Goal is The Same = Deliver Real Value to
Users
Let’s Collaborate and Believe “Together, We Can!” Collaborations ・・・ ・・・
・・・ ・・・ ・・・ ・・・
Move as one, Achieve more.