howtheysre

KO | EN

gitlite — search

#javascript #ai #typescript #llm #golang #android #macos #nodejs #cli #vue #awesome-list #pytorch #security #openai

(★ 9,800)

전 세계의 기술 기업과 기술 역량이 뛰어난 조직들이 Site Reliability Engineering (SRE)을 실천하는 방법에 관해 공개된 리소스들을 엄선한 모음집입니다.

파일 탐색기

최종 버전 다운로드 (.zip)

- - codeql.yml
  - dependabot.yml
  - workflow.yml
- .eslintrc.js
- .markdownlint.json
- main.spec.js
- package-lock.json
- package.json
.gitattributes
.gitignore
code-of-conduct.md
contributing.md
headline.png
LICENSE
README.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# How they SRE
![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square) [![CI](https://github.com/upgundecha/howtheysre/actions/workflows/workflow.yml/badge.svg)](https://github.com/upgundecha/howtheysre/actions/workflows/workflow.yml) [![CodeQL](https://github.com/upgundecha/howtheysre/actions/workflows/codeql.yml/badge.svg)](https://github.com/upgundecha/howtheysre/actions/workflows/codeql.yml)
![How they SRE](https://raw.githubusercontent.com/upgundecha/howtheysre/main/headline.png)
## 소개
\_\_How They SRE\_\_는 선도적인 기술 기업 및 IT 친화적인 조직들이 채택한 Site Reliability Engineering (SRE) 모범 사례, 도구, 기법, 그리고 문화를 모아둔 지식 저장소입니다.
수많은 조직들이 엔지니어링 블로그, 컨퍼런스, 밋업 등 다양한 공개 플랫폼을 통해 자신들의 엔지니어링 문화를 형성하는 모범 사례, 도구, 기법을 포함한 통찰력과 전문 지식을 빈번하게 공유하고 있습니다. 본 저장소는 이러한 출처에서 수집한 콘텐츠를 컴파일하여 제공합니다.
### 주제
\* Site Reliability Engineering
\* SRE 팀 채용 및 구축
\* SRE 문화
\* DevOps
\* Monitoring & Observability
\* Alerting
\* Incident Response & Post-Mortem
\* On-Call
\* Testing in Production
\* Chaos Engineering
\* Automation
\* Performance
\* Platform Engineering
## 조직
Achievers
### 블로그 글
\* [Enter the Abattoir - Building 'à la carte' gitops tooling](https://achievers.engineering/enter-the-abattoir-ee5e2019f0b3)
\* [Scaling Production Globally — The service mesh facelift (Part-1)](https://achievers.engineering/scaling-production-globally-service-mesh-face-lift-part-1-30ad6d393d04)
\* [Scaling Production Globally - Solving observability problems for developers (Part-2)](https://achievers.engineering/scaling-production-globally-solving-observability-problems-for-developers-part-2-b5416ce5eb8a)
\* [Load Testing Kubernetes: Building a Framework (Part-1)](https://achievers.engineering/load-testing-kubernetes-building-a-framework-part-1-bdc0af4ae7e2)
\* [Load Testing Kubernetes: Resolving bottlenecks and improving performance (Part-2)](https://achievers.engineering/load-testing-kubernetes-resolving-bottlenecks-and-improving-performance-part-2-c4f08102f105)

Airbnb
### 블로그 글
\* [Automated Incident Management Through Slack](https://medium.com/airbnb-engineering/incident-management-ae863dc5d47f)
\* [Detecting Vulnerabilities With Vulnture](https://medium.com/airbnb-engineering/detecting-vulnerabilities-with-vulnture-f5f23387f6ec)
\* [Alerting Framework at Airbnb](https://medium.com/airbnb-engineering/alerting-framework-at-airbnb-35ba48df894f)
\* [When The Cloud Gets Dark — How Amazon’s Outage Affected Airbnb](https://medium.com/airbnb-engineering/when-the-cloud-gets-dark-how-amazons-outage-affected-airbnb-66eaf8c0f162)
\* [Intelligent Automation Platform: Empowering Conversational AI and Beyond at Airbnb](https://medium.com/airbnb-engineering/intelligent-automation-platform-empowering-conversational-ai-and-beyond-at-airbnb-869c44833ff2)
\* [Production Secret Management at Airbnb](https://medium.com/airbnb-engineering/production-secret-management-at-airbnb-ad230e1bc0f6)
\* [Automating Data Protection at Scale, Part 1](https://medium.com/airbnb-engineering/automating-data-protection-at-scale-part-1-c74909328e08)
\* [Automating Data Protection at Scale, Part 2](https://medium.com/airbnb-engineering/automating-data-protection-at-scale-part-2-c2b8d2068216)
\* [Automating Data Protection at Scale, Part 3](https://medium.com/airbnb-engineering/automating-data-protection-at-scale-part-3-34e592c45d46)
\* [Dynamic Kubernetes Cluster Scaling at Airbnb](https://medium.com/airbnb-engineering/dynamic-kubernetes-cluster-scaling-at-airbnb-d79ae3afa132)

Algolia
### Blog Posts
\* [May 30 SSL incident](https://www.algolia.com/blog/may-30-ssl-incident/)
\* [A Journey Into SRE](https://www.algolia.com/blog/a-journey-into-sre/)
\* [CI/CDay 2024: What makes a good CI/CD platform?](https://www.algolia.com/blog/engineering/cicday-2024-what-makes-a-good-ci-cd-platform/)

Alibaba Cloud
### Blog Posts
\* [Why Are the Top Internet Companies Choosing SRE over Traditional O&M?](https://www.alibabacloud.com/blog/why-are-the-top-internet-companies-choosing-sre-over-traditional-o%26m\_596099)
\* [Architecture and Practices of Bilibili's Real-time Platform](https://www.alibabacloud.com/blog/architecture-and-practices-of-bilibilis-real-time-platform\_596676)

Asana
### Blog Posts
\* [How Asana uses Asana: Security incident response](https://blog.asana.com/2021/09/engineering-security-incident-response/#close)
\* [How Asana ships stable web application releases](https://blog.asana.com/2021/01/asana-engineering-ships-web-application-releases/)
\* [Analysis of recent downtime & what we’re doing to prevent future incidents](https://blog.asana.com/2019/09/downtime-what-were-doing-to-prevent-future-downtime/)
\* [Developer environment: Achieving reliability by making it fast to reset](https://blog.asana.com/2017/07/developer-environment-making-it-reliable-by-making-it-fast-to-reset/)
\* [Three security tactics for every IT leader to consider this fall](https://blog.asana.com/2022/08/it-security-hybrid-workers/)

ASOS
### Blog Posts
\* [Playing the blame-less game](https://medium.com/asos-techblog/playing-the-blame-less-game-3708f8195344)
\* [A day in the life of… Cat S (Head of Reliability Engineering)](https://medium.com/asos-techblog/a-day-in-the-life-of-cat-smith-head-of-reliability-engineering-629e10a26590)
\* [An AKS Performance Journey: Part 1 — Sizing Everything Up](https://medium.com/asos-techblog/an-aks-performance-journey-part-1-sizing-everything-up-ee6d2346ea99)
\* [An AKS Performance Journey: Part 2 — Networking It Out](https://medium.com/asos-techblog/an-aks-performance-journey-part-2-networking-it-out-e253f5bb4f69)
\* [Cyber Security @ ASOS.com](https://medium.com/asos-techblog/cyber-security-asos-com-7d1d1f346e57)
\* [Security Operations 24x7](https://medium.com/asos-techblog/security-operations-24-x-7-2e90c8e5e7e)
\* [The skills we look for in Cyber Security Incident Response](https://medium.com/asos-techblog/the-skills-we-look-for-in-cyber-security-incident-response-12b327927e38)

Atlassian
### Blog Posts
\* [Best practices for change management in the age of DevOps](https://www.atlassian.com/engineering/best-practices-for-change-management-in-the-age-of-devops)
\* [Automated testing: 5 lessons from Atlassian’s Kubernetes team on testing infrastructure as code](https://www.atlassian.com/engineering/automated-testing-5-lessons-from-atlassians-kubernetes-team-on-testing-infrastructure-as-code)
\* [How to export Kubernetes events for observability and alerting](https://www.atlassian.com/engineering/how-to-export-kubernetes-events-for-observability-and-alerting)
\* [Incident Postmortem Template](https://www.atlassian.com/incident-management/postmortem/templates)

BackMarket
### Blog Posts
\* [How Back Market SREs prepared for Black Friday](https://medium.com/back-market-engineering/how-back-market-sres-prepared-for-black-friday-5f017f343408)

Baidu
### Videos
\* [Anomaly Detection on Golden Signals](https://www.usenix.org/conference/srecon19asia/presentation/chen-yu)
\* [NetRadar: Monitoring the Datacenter Network](https://www.usenix.org/conference/srecon19asia/presentation/chen-yun)
\* [Let the Chaos Begin—SRE Chaos Engineering Meets Cybersecurity](https://www.youtube.com/watch?v=x3c0PPkSf14)

Basecamp
### 블로그 게시물
\* [Inside a CODE RED: Network Edition](https://m.signalvnoise.com/inside-a-code-red-network-edition/)
\* [Three Basecamp outages. One week. What happened?](https://m.signalvnoise.com/three-basecamp-outages-one-week-what-happened/)
\* [Basecamp 2 and Basecamp 3 search outage report](https://m.signalvnoise.com/basecamp-2-and-basecamp-3-search-outage-report/)
\* [Reducing Incident Escalations at Basecamp](https://m.signalvnoise.com/reducing-incident-escalations-at-basecamp/)
### 도서
\* [Shape Up](https://basecamp.com/shapeup/webbook)

Bloomberg
### 동영상
\* [Capacity Planning and Performance Enhancement with Page Reference Sampling](https://www.usenix.org/conference/srecon20americas/presentation/chen)
\* [Why SREs can't afford to NOT do Chaos Engineering](https://www.usenix.org/conference/srecon20americas/presentation/pawlikowski)
\* [Tracing Real-Time Distributed Systems](https://www.usenix.org/conference/srecon19emea/presentation/yakimov)
\* [The Bloomberg Story: Building SRE Teams in an "Immeasurable" Organisation](https://www.usenix.org/conference/srecon19asia/presentation/sorensen)
\* [Visibility into Loggers (and Other Low Level Services)—Seeing the Trees from the Forest](https://www.usenix.org/conference/srecon19americas/presentation/chen)

Booking.com
### 블로그 게시물
\* [How Reliability and Product Teams Collaborate at Booking.com](https://medium.com/booking-com-infrastructure/how-reliability-and-product-teams-collaborate-at-booking-com-f6c317cc0aeb)
\* [Incidents, fixes, and the day after](https://medium.com/booking-com-infrastructure/incidents-fixes-and-the-day-after-c5d9aeae28c3)
\* [Troubleshooting: A journey into the unknown](https://medium.com/booking-com-infrastructure/troubleshooting-a-journey-into-the-unknown-e31b524fa86)
### 동영상
\* [Sailing the Database Seas: Applying SRE Principles at Scale](https://www.usenix.org/conference/srecon24emea/presentation/androulidakis)
\* [SLOs for Data-Intensive Services](https://www.usenix.org/conference/srecon19emea/presentation/fouquet)
\* [Benefits of Taking the Less Traveled Road with Containers Infrastructure](https://www.usenix.org/conference/srecon19americas/presentation/iacoboaia)

Capital One
### 블로그 게시물
\* [Automate Application Monitoring with Slack](https://www.capitalone.com/tech/software-engineering/how-to-automate-application-monitoring-slack-bots/)
\* [Automate AWS Infrastructure with Boto 3: AWS Health Check](https://medium.com/capital-one-tech/automate-aws-infrastructure-with-boto-3-aws-health-checks-e51338ba075)
\* [Active-Active Shared-Nothing Database Architecture](https://medium.com/capital-one-tech/active-active-shared-nothing-database-architecture-304957ffb89)
\* [The 3 R’s of SREs: Resiliency, Recovery & Reliability](https://medium.com/capital-one-tech/the-3-rs-of-sres-resiliency-recovery-reliability-5f2f5360a91b)
\* [5 Steps to Getting Your App Chaos Ready](https://medium.com/capital-one-tech/5-steps-to-getting-your-app-chaos-ready-capital-one-a5b7b3cb8e09)
\* [4 Real-World Scenarios That Read Like Chaos Engineering Experiments](https://medium.com/capital-one-tech/4-real-world-scenarios-that-read-like-chaos-engineering-experiments-8dbf40c5f247)
\* [Embrace the Chaos … Engineering](https://medium.com/capital-one-tech/embrace-the-chaos-engineering-203fd6fc6ff7)
\* [3 Lessons Learned From Implementing Chaos Engineering at Enterprise](https://medium.com/capital-one-tech/3-lessons-learned-from-implementing-chaos-engineering-at-enterprise-28eb3ffecc57)
\* [A Deep Dive Into Seamless Blue/Green Deployment Using AWS CodeDeploy](https://medium.com/capital-one-tech/seamless-blue-green-deployment-using-aws-codedeploy-4c36c0bbeef4)
\* [Secure Docker Containers Require Secure Applications](https://medium.com/capital-one-tech/secure-docker-containers-require-secure-applications-75eb358abef9)
\* [4 Steps for Pairing the Cloud and DevOps to Improve Resiliency](https://medium.com/capital-one-tech/4-steps-for-pairing-cloud-and-devops-to-improve-resiliency-c72fe2e52b05)
\* [Container Ready Applications with Twelve-Factor App and Microservices Architecture](https://medium.com/capital-one-tech/container-ready-applications-with-twelve-factor-app-and-microservices-architecture-16af683a767f)
\* [Deploying with Confidence — Minimize Risk, Maximize Resiliency With Canary Deployments on AWS](https://medium.com/capital-one-tech/deploying-with-confidence-strategies-for-canary-deployments-on-aws-7cab3798823e)
\* [Architecting for Resiliency](https://medium.com/capital-one-tech/architecting-for-resiliency-9ec663db5c94)
\* [Continuous Chaos — Introducing Chaos Engineering into DevOps Practices](https://medium.com/capital-one-tech/continuous-chaos-introducing-chaos-engineering-into-devops-practices-75757e1cca6d)
\* [The Mon-ifesto Part 1: Metrics](https://medium.com/capital-one-tech/the-mon-ifesto-part-1-metrics-808f6c944765)
### 주요 인시던트 및 분석 보고서
\* [Information on the Capital One Cyber Incident](https://www.capitalone.com/facts2019/)
\* [A Case Study of the Capital One Data Breach](http://web.mit.edu/smadnick/www/wp/2020-16.pdf)
### 동영상
\* [Banking on Continuous Delivery - Capital One](https://www.youtube.com/watch?v=\_DnYSQEUTfo)
\* [Continuous Chaos in DevOps - Capital One](https://www.youtube.com/watch?v=U\_Uh5RMCwPI)
\* [DevOps at Capital One: Focusing on Pipeline and Measurement](https://www.youtube.com/watch?v=6Q0mtVnnthQ)
\* [Automating the Management of the Operational Health of Cloud Accounts at Scale](https://www.usenix.org/conference/srecon19americas/presentation/walls)

Coinbase
### 블로그 게시물
\* [Open Sourcing Coinbase’s Secure Deployment Pipeline](https://blog.coinbase.com/open-sourcing-coinbases-secure-deployment-pipeline-ae6c78e25517)

DAZN
### 블로그 게시물
\* [Site Reliability at DAZN](https://medium.com/dazn-tech/site-reliability-at-dazn-a3ba4af0638d)

DBS
### 블로그 게시물
\* [iThome SRE 콘퍼런스 발표: 지금까지의 DBS SRE 전환 여정](https://medium.com/dbs-tech-blog/presenting-at-ithomes-sre-conference-our-dbs-sre-transformation-journey-thus-far-9b6778ce53e8)
\* [가장 인기 있는 SRE(Site Reliability Engineering) 미신 7가지 바로 잡기](https://medium.com/dbs-tech-blog/debunking-the-seven-most-popular-site-reliability-engineering-myths-a3be8d870ff2)
\* [SRE를 사용하여 직장에서 비난 없는 문화를 배양하는 방법](https://medium.com/dbs-tech-blog/how-to-use-sre-to-cultivate-a-blameless-culture-in-the-workplace-1981fd1c7871)
\* [DBS Bank의 Site Reliability Engineering](https://medium.com/dbs-tech-blog/site-reliability-engineering-at-dbs-bank-32c02228ccf4)
\* [대규모 구성 관리 자동화](https://medium.com/dbs-tech-blog/automating-configuration-management-at-scale-5c7927f83df3)
\* [DBS가 Chaos Engineering의 미신을 해소한 방법](https://medium.com/dbs-tech-blog/how-dbs-dispelled-the-myths-of-chaos-engineering-e5873ac78c9)
\* [수고와 고생을 거듭하며: DevOps 팀의 단순 반복 업무(Toil)를 줄이기 위해 SRE 관행 적용하기](https://medium.com/dbs-tech-blog/double-double-toil-and-trouble-applying-sre-practices-to-alleviate-toil-for-devops-teams-259b958a10dd)
### 동영상
\* [SREcon Conversations 아시아/태평양, Koon Seng Lim (DBS)](https://www.youtube.com/watch?v=URwkaRbOLxI&feature=emb\_title)

DeepSource
### 블로그 게시물
\* [Redis 디스크리스 복제: 내용, 방식, 이유 및 주의사항](https://deepsource.io/blog/redis-diskless-replication/)
\* [Kubernetes에 Vault 설정하는 방법](https://deepsource.io/blog/setup-vault-kubernetes/)
\* [Kubernetes에서의 무중단 배포 분석](https://deepsource.io/blog/zero-downtime-deployment/)

Dream11
### 블로그 게시물
\* [대규모 배포: Dream11의 자체 블루투린(Blue-Green) 배포 플랫폼 'OneClick'의 비하인드 스토리](https://blog.dream11engineering.com/deployment-at-scale-story-behind-dream11s-in-house-blue-green-deployment-platform-oneclick-b2c761b12896)
\* [AWS WAFv2를 통한 보안 및 신뢰성 강화](https://blog.dream11engineering.com/enhancing-security-and-trust-with-aws-wafv2-8b050b1cba37)
\* [대규모로 GraphQL을 운영하며 얻은 교훈](https://blog.dream11engineering.com/lessons-learned-from-running-graphql-at-scale-2ad60b3cefeb)
\* [회로를 차단하고, Kong을 구하세요 🦍](https://blog.dream11engineering.com/break-circuits-save-kong-3680d88a0639)
\* [혼돈 속에서 질서 찾기: Torque를 사용하여 성능 테스트를 자동화한 방법](https://blog.dream11engineering.com/finding-order-in-chaos-how-we-automated-performance-testing-with-torque-6eb63706fcea)
\* [Dream11에서 초음속 릴리스 유지하기](https://blog.dream11engineering.com/maintaining-hyper-sonic-releases-at-dream11-c26f2145fe28)
\* [스케일 인 또는 스케일 아웃? Dream11의 확장 방식](https://blog.dream11engineering.com/to-scale-in-or-scale-out-heres-how-we-scale-at-dream11-f88ef5e71cbc)
\* [Dream11에서 확장 가능한 실시간 분석, 알림 및 이상 징후 감지 아키텍처 구축하기](https://blog.dream11engineering.com/building-scalable-real-time-analytics-alerting-and-anomaly-detection-architecture-at-dream11-e20edec91d33)

Dropbox
### 블로그 게시물
\* [Dropbox Engineering Career Framework - Reliability Engineer (SRE)](https://dropbox.github.io/dbx-career-framework/)
\* [Atlas: Our journey from a Python monolith to a managed platform](https://dropbox.tech/infrastructure/atlas--our-journey-from-a-python-monolith-to-a-managed-platform)
\* [Monitoring server applications with Vortex](https://dropbox.tech/infrastructure/monitoring-server-applications-with-vortex)
\* [Athena: Our automated build health management system](https://dropbox.tech/infrastructure/athena-our-automated-build-health-management-system)
\* [Interested in becoming a Site Reliability Engineer?](https://tammybutow.medium.com/graduating-from-bootcamp-and-interested-in-becoming-a-site-reliability-engineer-b69a38ce858b)
### 동영상
\* [Service Discovery Challenges at Scale](https://www.usenix.org/conference/srecon19americas/presentation/nigmatullin)

eBay
### 블로그 게시물
\* [Resiliency and Disaster Recovery with Kafka](https://tech.ebayinc.com/engineering/resiliency-and-disaster-recovery-with-kafka/)
\* [SRE Case Study: Triaging a Non-Heap JVM Out of Memory Issue](https://tech.ebayinc.com/engineering/sre-case-study-triage-a-non-heap-jvm-out-of-memory-issue/)
\* [SRE Case Study: Mysterious Traffic Imbalance](https://tech.ebayinc.com/engineering/sre-case-study-mysterious-traffic-imbalance/)
\* [Zero Downtime, Instant Deployment and Rollback](https://tech.ebayinc.com/engineering/zero-downtime-instant-deployment-and-rollback/)
\* [How eBay’s Notification Platform Used Fault Injection in New Ways](https://innovation.ebayinc.com/tech/engineering/how-ebays-notification-platform-used-fault-injection-in-new-ways/)
### 동영상
\* [Madaari: Ordering for the Monkeys](https://www.usenix.org/conference/srecon19americas/presentation/raina)

Epic Games
### 동영상
\* [AWS re:Invent 2018: Epic Games Uses AWS to Deliver Fortnite to 200 Million Players](https://youtu.be/MCLrA401vHw)

Etsy
### 블로그 게시물
\* [Improving the Deployment Experience of a Ten-Year Old Application](https://codeascraft.com/)
\* [How Etsy Prepared for Historic Volumes of Holiday Traffic in 2020](https://codeascraft.com/2021/02/25/how-etsy-prepared-for-historic-volumes-of-holiday-traffic-in-2020/)
\* [Your brain on progress](https://increment.com/reliability/brain-on-progress/)
\* [Etsy’s Debriefing Facilitation Guide for Blameless Postmortems](https://codeascraft.com/2016/11/17/debriefing-facilitation-guide/)
\* [Opsweekly: Measuring on-call experience with alert classification](https://codeascraft.com/2014/06/19/opsweekly-measuring-on-call-experience-with-alert-classification/)
\* [Demystifying Site Outages](https://blog.etsy.com/news/2012/demystifying-site-outages/)
\* [Blameless PostMortems and a Just Culture](https://codeascraft.com/2012/05/22/blameless-postmortems/)
\* [Measure Anything, Measure Everything](https://codeascraft.com/2011/02/15/measure-anything-measure-everything/)
### 동영상
\* [Velocity 09: John Allspaw and Paul Hammond, "10+ Deploys Pe](https://www.youtube.com/watch?v=LdOe18KhtT4)
\* [Migrating a Monolith to the Cloud](https://www.usenix.org/conference/srecon19americas/presentation/govande)

Expedia
### Blog Posts
\* [Automating Performance Standards](https://medium.com/expedia-group-tech/automating-performance-standards-b51efc92d237)
\* [Error Budget Policy - Part 1 - Adoption at Expedia Group](https://medium.com/expedia-group-tech/error-budget-policy-adoption-at-expedia-group-7d80d41c4a8b)
\* [Error Budget Policy - Part 2 - Practices at Expedia Group](https://medium.com/expedia-group-tech/error-budget-policies-in-practice-4c98f56a28c1)
\* [Using Fault-Injection to Improve our new Runtime Platform’s Reliability](https://medium.com/expedia-group-tech/using-fault-injection-to-improve-our-new-platforms-reliability-656b1147b132)
\* [Learning from Incidents at Expedia Group](https://medium.com/expedia-group-tech/learning-from-incidents-at-expedia-group-51a8c72a4286)
\* [Improving Vrbo Homepage Loading Experience](https://medium.com/expedia-group-tech/improving-vrbo-homepage-loading-experience-e4b2207535f4)
\* [Troubleshooting 502 errors: ECS Checklist](https://medium.com/expedia-group-tech/troubleshooting-502-errors-ecs-checklist-9da383399d96)
\* [Getting Started with Elasticsearch](https://medium.com/expedia-group-tech/getting-started-with-elastic-search-6af62d7df8dd)
\* [All about ISTIO-PROXY 5xx Issues](https://medium.com/expedia-group-tech/all-about-istio-proxy-5xx-issues-e0221b29e692)
\* [Autoscaling in Kubernetes: Why doesn’t the Horizontal Pod Autoscaler work for me?](https://medium.com/expedia-group-tech/autoscaling-in-kubernetes-why-doesnt-the-horizontal-pod-autoscaler-work-for-me-5f0094694054)
\* [How to Keep Your Kubernetes Deployments Balanced Across Multiple zones](https://medium.com/expedia-group-tech/how-to-keep-your-kubernetes-deployments-balanced-across-multiple-zones-dfe719847b41)
\* [Are Your Dropwizard Latency Metrics Misleading You?](https://medium.com/expedia-group-tech/your-latency-metrics-could-be-misleading-you-how-hdrhistogram-can-help-9d545b598374)
\* [The Cost of 100% Reliability](https://medium.com/expedia-group-tech/the-cost-of-100-reliability-ecb2901f23a4)
\* [Creating Monitoring Dashboards](https://medium.com/expedia-group-tech/creating-monitoring-dashboards-1f3fbe0ae1ac)
\* [Using Bash for DevOps](https://medium.com/expedia-group-tech/using-bash-for-devops-7046eed1aa63)

Fastly
### Videos
\* [SRE & Product Management: How to Level up Your Team (and Career!) by Thinking like a Product Manager](https://www.usenix.org/conference/srecon19americas/presentation/wohlner)
\* [Resilience Engineering Mythbusting](https://www.usenix.org/conference/srecon19americas/presentation/gallego)

G-Research
### Blog Posts
\* [Our SRE Journey at G-Research](https://www.gresearch.com/blog/article/our-sre-journey-at-g-research/)
\* [The SRE Journey Continues](https://www.gresearch.com/blog/article/the-sre-journey-continues/)
\* [OpenTSDB Meta Cache – trade-offs for performance](https://www.gresearch.com/blog/article/opentsdb-meta-cache-trade-offs-for-performance/)

Getaround
### Blog Posts
\* [How we handle incidents at Getaround](https://getaround.tech/incident-handling-at-getaround/)
\* [Evolution Of Our Continuous Delivery Process](https://getaround.tech/continuous-integration/)

GitHub
### 블로그 게시물
\* [반복적인 단순화를 통해 가용성을 개선한 방법](https://github.blog/engineering/engineering-principles/how-we-improved-availability-through-iterative-simplification/)
\* [GitHub에서 푸시 처리를 개선한 방법](https://github.blog/engineering/architecture-optimization/how-we-improved-push-processing-on-github/)
\* [GitHub가 merge queue를 사용하여 매일 수백 개의 변경 사항을 배포하는 방법](https://github.blog/engineering/engineering-principles/how-github-uses-merge-queue-to-ship-hundreds-of-changes-every-day/)
\* [AI로 보안 취약점 해결하기](https://github.blog/engineering/platform-security/fixing-security-vulnerabilities-with-ai/)
\* [GitHub의 Engineering Fundamentals 프로그램: 가용성, 보안, 접근성을 달성하는 방법](https://github.blog/engineering/engineering-principles/githubs-engineering-fundamentals-program-how-we-deliver-on-availability-security-and-accessibility/)
\* [GitHub가 GitHub Actions 및 Actions larger runners를 사용하여 GitHub.com을 빌드하고 테스트하는 방법](https://github.blog/2023-09-26-how-github-uses-github-actions-and-actions-larger-runners-to-build-and-test-github-com/)
\* [오픈 소스 프로젝트에서 500개의 CVE를 공개한 The GitHub Security Lab의 여정](https://github.blog/2023-09-21-the-github-security-labs-journey-to-disclosing-500-cves-in-open-source-projects/)
\* [CodeQL 팀이 AI를 활용해 코드 내 취약점 탐지를 강화하는 방법](https://github.blog/2023-09-12-codeql-team-uses-ai-to-power-vulnerability-detection-in-code/)
\* [GitHub의 최근 가용성 문제 해결하기](https://github.blog/2023-05-16-addressing-githubs-recent-availability-issues/)
\* [GitHub Actions를 통한 CI/CD 및 자동화의 조직 전반 거버넌스 및 재사용 구축](https://github.blog/2023-04-05-building-organization-wide-governance-and-re-use-for-cicd-and-automation-with-github-actions/)
\* [GitHub Actions와 IssueOps를 통한 브랜치 배포 활성화](https://github.blog/2023-02-02-enabling-branch-deployments-through-issueops-with-github-actions/)
\* [ChatOps를 사용하여 Actions 온콜 엔지니어 돕기](https://github.blog/2021-12-01-using-chatops-to-help-actions-on-call-engineers/)
\* [규모 확장을 위한 GitHub의 관계형 데이터베이스 파티셔닝](https://github.blog/2021-09-27-partitioning-githubs-relational-databases-scale/)
\* [GitHub code scanning으로 개발자 만족도 높이기](https://github.blog/2021-09-07-increasing-developer-happiness-github-code-scanning/)
\* [GitHub가 OpenTelemetry를 도입하는 이유 (및 방법)](https://github.blog/2021-05-26-why-and-how-github-is-adopting-opentelemetry/)
\* [GitHub에서 대규모 모노레포 성능 개선하기](https://github.blog/2021-03-16-improving-large-monorepo-performance-on-github/)
\* [GitHub의 배포 안정성](https://github.blog/2021-02-03-deployment-reliability-at-github/)
\* [GitHub 배포 방식 개선하기](https://github.blog/2021-01-25-improving-how-we-deploy-github/)
\* [GitHub의 온콜 문화 구축하기](https://github.blog/2021-01-06-building-on-call-culture-at-github/)
\* [불안정한 빌드(Flaky build) 18배 줄이기](https://github.blog/2020-12-16-reducing-flaky-builds-by-18x/)
\* [DevOps에서 운영의 진화하는 역할](https://github.blog/2020-12-03-the-evolving-role-of-operations-in-devops/)
\* [DevOps 자동화 시작하기](https://github.blog/2020-10-29-getting-started-with-devops-automation/)
\* [GitHub의 MySQL 고가용성](https://github.blog/2018-06-20-mysql-high-availability-at-github/)
### 주요 장애 및 분석 보고서
\* [GitHub 가용성 보고서: 2024년 8월](https://github.blog/news-insights/company-news/github-availability-report-august-2024/)
\* [GitHub 가용성 보고서: 2024년 7월](https://github.blog/news-insights/company-news/github-availability-report-july-2024/)
\* [GitHub 가용성 보고서: 2024년 6월](https://github.blog/news-insights/company-news/github-availability-report-june-2024/)
\* [GitHub 가용성 보고서: 2024년 5월](https://github.blog/news-insights/compan

y-news/github-availability-report-may-2024/)
\* [GitHub Availability Report: 2024년 4월](https://github.blog/news-insights/company-news/github-availability-report-april-2024/)
\* [GitHub Availability Report: 2024년 3월](https://github.blog/news-insights/company-news/github-availability-report-march-2024/)
\* [GitHub Availability Report: 2024년 2월](https://github.blog/news-insights/company-news/github-availability-report-february-2024/)
\* [GitHub Availability Report: 2024년 1월](https://github.blog/news-insights/company-news/github-availability-report-january-2024/)
\* [GitHub Availability Report: 2023년 12월](https://github.blog/news-insights/company-news/github-availability-report-december-2023/)
\* [GitHub Availability Report: 2023년 11월](https://github.blog/news-insights/company-news/github-availability-report-november-2023/)
\* [GitHub Availability Report: 2023년 10월](https://github.blog/news-insights/company-news/github-availability-report-october-2023/)
\* [GitHub Availability Report: 2023년 9월](https://github.blog/news-insights/company-news/github-availability-report-september-2023/)
\* [GitHub Availability Report: 2023년 8월](https://github.blog/2023-09-13-github-availability-report-august-2023/)
\* [GitHub Availability Report: 2023년 7월](https://github.blog/2023-08-09-github-availability-report-july-2023/)
\* [GitHub Availability Report: 2023년 6월](https://github.blog/2023-07-12-github-availability-report-june-2023/)
\* [GitHub Availability Report: 2023년 5월](https://github.blog/2023-06-14-github-availability-report-may-2023/)
\* [GitHub Availability Report: 2023년 4월](https://github.blog/2023-05-03-github-availability-report-april-2023/)
\* [GitHub Availability Report: 2023년 3월](https://github.blog/2023-04-05-github-availability-report-march-2023/)
\* [GitHub Availability Report: 2023년 2월](https://github.blog/2023-03-01-github-availability-report-february-2023/)
\* [GitHub Availability Report: 2023년 1월](https://github.blog/2023-02-01-github-availability-report-january-2023/)
\* [GitHub Availability Report: 2022년 12월](https://github.blog/2023-01-04-github-availability-report-december-2022/)
\* [GitHub Availability Report: 2022년 11월](https://github.blog/2022-12-07-github-availability-report-november-2022/)
\* [GitHub Availability Report: 2022년 10월](https://github.blog/2022-11-02-github-availability-report-october-2022/)
\* [GitHub Availability Report: 2022년 9월](https://github.blog/2022-10-05-github-availability-report-september-2022/)
\* [GitHub Availability Report: 2022년 8월](https://github.blog/2022-09-07-github-availability-report-august-2022/)
\* [GitHub Availability Report: 2022년 7월](https://github.blog/2022-08-03-github-availability-report-july-2022/)
\* [GitHub Availability Report: 2022년 6월](https://github.blog/2022-07-06-github-availability-report-june-2022/)
\* [GitHub Availability Report: 2022년 5월](https://github.blog/2022-06-01-github-availability-report-may-2022/)
\* [GitHub Availability Report: 2022년 4월](https://github.blog/2022-05-04-github-availability-report-april-2022/)
\* [GitHub Availability Report: 2022년 3월](https://github.blog/2022-04-06-github-availability-report-march-2022/)
\* [GitHub Availability Report: 2022년 2월](https://github.blog/2022-03-02-github-availability-report-february-2022/)
\* [GitHub Availability Report: 2022년 1월](https://github.blog/2022-02-02-github-availability-report-january-2022/)
\* [GitHub Availability Report: 2021년 12월](https://github.blog/2022-01-05-github-availability-report-december-2021/)
\* [GitHub Availability Report: 2021년 11월](https://github.blog/2021-12-01-github-availability-report-november-2021/)
\* [GitHub Availability Report: 2021년 10월](https://github.blog/2021-11-04-github-availability-report-october-2021/)
\* [GitHub Availability Report: 2021년 9월](https://github.blog/2021-10-06-github-availability-report-september-2021/)
\* [GitHub Availability Report: 2021년 8월](https://gith

ub.blog/2021-09-01-github-availability-report-august-2021/)
\* [GitHub Availability Report: July 2021](https://github.blog/2021-08-04-github-availability-report-july-2021/)
\* [GitHub Availability Report: June 2021](https://github.blog/2021-07-07-github-availability-report-june-2021/)
\* [GitHub Availability Report: May 2021](https://github.blog/2021-06-02-github-availability-report-may-2021/)
\* [GitHub Availability Report: April 2021](https://github.blog/2021-05-05-github-availability-report-april-2021/)
\* [GitHub Availability Report: March 2021](https://github.blog/2021-04-07-github-availability-report-march-2021/)
\* [GitHub Availability Report: February 2021](https://github.blog/2021-03-03-github-availability-report-february-2021/)
\* [GitHub Availability Report: January 2021](https://github.blog/2021-02-02-github-availability-report-january-2021/)
\* [GitHub Availability Report: December 2020](https://github.blog/2021-01-06-github-availability-report-december-2020/)
\* [GitHub Availability Report: November 2020](https://github.blog/2020-12-02-availability-report-november-2020/)
\* [GitHub Availability Report: August 2020](https://github.blog/2020-09-02-github-availability-report-august-2020/)
\* [GitHub Availability Report: July 2020](https://github.blog/2020-08-05-github-availability-report-july-2020/)
\* [Introducing the GitHub Availability Report](https://github.blog/2020-07-08-introducing-the-github-availability-report/)
\* [February service disruptions post-incident analysis](https://github.blog/2020-03-26-february-service-disruptions-post-incident-analysis/)
\* [October 21 post-incident analysis](https://github.blog/2018-10-30-oct21-post-incident-analysis/)
\* [February 28th DDoS Incident Report](https://github.blog/2018-03-01-ddos-incident-report/)
\* [Incident Report: Inadvertent Private Repository Disclosure](https://github.blog/2016-10-28-incident-report-inadvertent-private-repository-disclosure/)
### Videos
\* [One on One SRE](https://www.usenix.org/conference/srecon19americas/presentation/tobey)

GitLab
### 블로그 게시물
\* [어느 SRE가 HAProxy 설정 변경을 시도했습니다. 다음으로 벌어진 일은 믿기 힘들 것입니다...](https://about.gitlab.com/blog/2021/01/14/this-sre-attempted-to-roll-out-an-haproxy-change/)
\* [GitLab Site Reliability Engineer 섀도잉 일주일기](https://about.gitlab.com/blog/2019/12/16/sre-shadow/)
\* [업데이트: Advanced Global Search를 위해 Elasticsearch에서 배운 교훈](https://about.gitlab.com/blog/2020/04/28/elasticsearch-update/)
\* [인프라 신규 팀이 반복(Iteration)을 통해 배운 것들](https://about.gitlab.com/blog/2020/11/09/lessons-in-iteration-from-new-infrastructure-team/)
\* [GitLab에서 인프라 비용을 최적화한 방법](https://about.gitlab.com/blog/2020/10/27/how-we-optimized-our-infrastructure-spend-at-gitlab/)
\* [Sidekiq을 사용하여 GitLab.com에서 비동기 작업 처리를 확장한 방법](https://about.gitlab.com/blog/2020/06/24/scaling-our-use-of-sidekiq/)
\* [GitLab 내부 들여다보기: 소프트웨어 패치를 배포하는 방법](https://about.gitlab.com/blog/2020/05/13/how-we-release-software-patches/)
\* [누락된 TCP Keepalive를 추적하면서 Docker, Golang, GitLab에 대해 배운 점](https://about.gitlab.com/blog/2019/11/15/tracking-down-missing-tcp-keepalives/)
\* [PostgreSQL을 활용한 재해 복구(Disaster Recovery)에 지연 복제(Delayed Replication)를 사용한 방법](https://about.gitlab.com/blog/2019/02/13/delayed-replication-for-disaster-recovery-with-postgresql/)

GoCardless
### 블로그 게시물
\* [GoCardless에서 소프트웨어 배포하기: "시작하기" 튜토리얼 오픈소스화](https://medium.com/gocardless-tech/deploying-software-at-gocardless-open-sourcing-our-getting-started-tutorial-ab857aa91c9e)
\* [Pub/Sub 메시지 등을 압축하여 막대한 비용을 절감한 방법](https://medium.com/gocardless-tech/how-we-compress-pub-sub-messages-and-more-saving-a-load-of-money-694b64c3458a)
\* [Rails를 위한 두려움 없는 PostgreSQL 마이그레이션](https://gocardless.com/blog/fear-free-postgresql-migrations-for-rails/)
\* [GoCardless의 관측 가능성(Observability): API 성능 개선 이야기](https://gocardless.com/blog/observability-at-gocardless-a-tale-of-api-performance-improvement/)
\* [PostgreSQL 쿼리 플래너 디버깅하기](https://gocardless.com/blog/debugging-the-postgres-query-planner/)
\* [다운타임 없는 Postgres 마이그레이션 - 어려운 부분들](https://gocardless.com/blog/zero-downtime-postgres-migrations-the-hard-parts/)
\* [성능을 찾아서 - 모든 POST 요청에서 200ms를 단축한 방법](https://gocardless.com/blog/in-search-of-performance-how-we-shaved-200ms-off-every-post-request/)
### 주요 인시던트 및 분석 보고서
\* [인시던트 검토: 2020년 10월 25일 서비스 중단, Vault TLS 만료](https://gocardless.com/blog/incident-review-service-outage-on-25-october-2020/)
\* [인시던트 검토: 2017년 10월 10일 API 및 대시보드 중단](https://gocardless.com/blog/incident-review-api-and-dashboard-outage-on-10th-october/)

GoDaddy
### 블로그 게시물
\* [Kubernetes 게이트 배포 (Gated Deployments)](https://www.godaddy.com/engineering/2019/08/13/kubernetes-gated-deployments/)
\* [Kubernetes 외부 시크릿 (External Secrets)](https://www.godaddy.com/engineering/2019/04/16/kubernetes-external-secrets/)
\* [Kubernetes - 애플리케이션 개발자를 위한 실용적인 입문서](https://www.godaddy.com/engineering/2018/05/02/kubernetes-introduction-for-developers/)
\* [Kubernetes API를 위한 직관적인 Node.js 클라이언트](https://www.godaddy.com/engineering/2018/04/10/an-intuitive-nodejs-client-for-the-kubernetes-api/)

Gojek
### 블로그 게시물
\* [Skynet 소개: Gojek을 위한 Infrastructure as Code](https://www.gojek.io/blog/introducing-skynet/)
\* [10배 늘어난 부하를 처리하기 위한 지리적 검색(Geo-Search) 서비스 확장](https://www.gojek.io/blog/scaling-our-geo-search-service-for-10x-load/)
\* [우리가 RCA(근본 원인 분석)를 신뢰하는 이유](https://www.gojek.io/blog/why-we-swear-by-the-rca)
\* [GKE에서 Kubernetes를 업그레이드하는 방법](https://blog.gojek.io/how-we-upgrade-kubernetes-on-gke/)
\* [프로덕션 환경에서 Apache Airflow를 모니터링하는 방법](https://blog.gojek.io/how-we-monitor-apache-airflow-in-production/)

Goldman Sachs
### 블로그 게시물
\* [SecDb Observability Journey](https://developer.gs.com/blog/posts/secdb-observability-journey)
\* [Chaos Testing an Application on AWS](https://developer.gs.com/blog/posts/chaos-testing-an-application-on-aws)
\* [머신러닝을 이용한 용량 장애 예측으로 애플리케이션 복원력 강화하기](https://developer.gs.com/blog/posts/forecasting-capacity-outages-using-machine-learning-to-bolster-application-resiliency)
\* [HAProxy를 사용하여 Sybase IQ Multiplexes로 99.9% 가용성 및 1초 미만의 응답 시간 제공하기](https://developer.gs.com/blog/posts/providing-999-availability-and-sub-second-response-times-with-sybase-iq-multiplexes-by-using-haproxy)
\* [Amazon RDS 및 Amazon Aurora로 멀티 리전 복원력 구축하기](https://developer.gs.com/blog/posts/building-multi-region-resiliency-with-amazon-rds-and-amazon-aurora)
\* [Goldman Sachs에서 고가용성 Trino Clusters 지원하기](https://developer.gs.com/blog/posts/enabling-highly-available-trino-clusters-at-goldman-sachs)
\* [대규모 관측가능성(Observability)](https://developer.gs.com/blog/posts/observability-at-scale)
\* [인프라와 커맨드 체인 패턴](https://developer.gs.com/blog/posts/infrastructure-and-command-chain-pattern)
\* [EC2 macOS를 활용한 모바일 CICD](https://developer.gs.com/blog/posts/mobile-cicd-with-ec2-macos)
\* [CatchIT 공개 - 소스 코드 시크릿 스캐너](https://developer.gs.com/blog/posts/catchit-source-code-secret-scanner)
\* [데이터 엔지니어링을 위한 플랫폼 구축](https://developer.gs.com/blog/posts/legend\_data\_engineering\_platforms)
### 동영상
\* [eBPF를 활용한 대규모 세부 CPU 용량 관리](https://www.usenix.org/conference/srecon24emea/presentation/brighton)

Google
### 블로그 게시물
\* [Accelerating incident response using generative AI](https://security.googleblog.com/2024/04/accelerating-incident-response-using.html)
\* [Pitfalls and Patterns in Microservice Dependency Management](https://www.infoq.com/articles/pitfalls-patterns-microservice-dependency-management/)
\* [SRE Practices & Processes](https://sre.google/resources/#practicesandprocesses)
\* [Google site reliability using Go](https://go.dev/solutions/google/sitereliability)
\* [Three months, 30x demand: How we scaled Google Meet during COVID-19](https://cloud.google.com/blog/products/g-suite/keeping-google-meet-ahead-of-usage-demand-during-covid-19)
\* [SRE Classroom: Distributed PubSub](https://sre.google/resources/practices-and-processes/distributed-pubsub/)
\* [How SRE teams are organized, and how to get started](https://cloud.google.com/blog/products/devops-sre/how-sre-teams-are-organized-and-how-to-get-started)
### 동영상
\* [Get Your Non-SREs Oncall Ready!](https://www.usenix.org/conference/srecon24emea/presentation/van-winkel)
\* [Reliable Data for Large ML Models: Principles and Practices](https://www.usenix.org/conference/srecon23emea/presentation/mcglohon)
\* [New Grads Becoming New SREs: Catalyzing a “Circle of Life” in Ireland](https://www.usenix.org/conference/srecon23emea/presentation/petoff)
\* [SRE for [cyber]security](https://www.usenix.org/conference/srecon23emea/presentation/fischbach)
\* [Artificial Intelligence: How Much Will It Cost You?](https://www.usenix.org/conference/srecon23emea/presentation/underwood)
\* [What's the Difference Between DevOps and SRE? with Seth Vargo and Liz Fong-Jones of Google](https://youtu.be/uTEL8Ff1Zvk)
\* [Risk and Error Budgets’ with Seth Vargo and Liz Fong-Jones of Google](https://youtu.be/y2ILKr8kCJU)
\* [Pragmatic Automation’ with Max Luebbe of GCP](https://www.youtube.com/watch?v=oDcjAcFTFC0&t=0m56s)
\* [Must Watch! - Google SRE YouTube Playlist](https://www.youtube.com/playlist?list=PLIivdWyY5sqJrKl7D2u-gmis8h9K66qoj)
\* [Squish Level Objectives: How SRE can Help Align Technical Work to User Benefit](https://www.usenix.org/conference/srecon20americas/presentation/stanke)
\* [Implementing Distributed Consensus](https://www.usenix.org/conference/srecon20americas/presentation/ludtke)
\* [The SRE I Aspire to Be](https://www.usenix.org/conference/srecon19emea/presentation/aknin)
\* [SRE Classroom, Or, How to Design a Reliable Distributed System in 3 Hours](https://www.usenix.org/conference/srecon19emea/presentation/perry)
\* [Zero Touch Prod: Towards Safer and More Secure Production Environments](https://www.usenix.org/conference/srecon19emea/presentation/czapinski)
\* [All of Our ML Ideas Are Bad (and We Should Feel Bad)](https://www.usenix.org/conference/srecon19emea/presentation/underwood)
\* [The Map Is Not the Territory: How SLOs Lead Us Astray, and What We Can Do about It](https://www.usenix.org/conference/srecon19emea/presentation/desai)
\* [Deploying SRE Training Best Practices to Production: How We SRE'ed Our SRE Education Program](https://www.usenix.org/conference/srecon19emea/presentation/petoff)
\* [Bigtable: A Journey from Binary to Service and the Lessons Learned along the Way](https://www.usenix.org/conference/srecon19emea/presentation/gleason)
\* [Practical Instrumentation for Observability](https://www.usenix.org/conference/srecon19asia/presentation/krabbe)
\* [What Is ML Ops: Solutions and Best Practices for DevOps of Production ML Services](https://www.usenix.org/conference/srecon19asia/presentation/sato)
\* [Unified Reporting of Service Reliability](https://www.usenix.org/conference/srecon19asia/presentation/zhang)
\* [How to Trade off Server Utilization and Tail Latency](https://www.usenix.org/conference/srecon19asia/presentation/plenz)
\* [Keeping the Balance: Internet-Scale Loadbalancing Demystified](https://www.usenix.org/conference/srecon19americas/presentation/nolan-loadbalancing)
\* [From Black Box to a Known Quantity: How to Build Predictable,

Reliable ML-based Services](https://www.usenix.org/conference/srecon19americas/presentation/virji)
\* [SRE에서의 마음챙김: 자기 자신을 위한 모니터링 및 알림](https://www.usenix.org/conference/srecon19americas/presentation/lutz)
\* [실용적인 자동화](https://www.usenix.org/conference/srecon19americas/presentation/luebbe)
\* [실무에서의 아선형 확장: 1k SRE 프로젝트](https://www.usenix.org/conference/srecon19americas/presentation/rath)
\* [프로덕션 데이터 수정 전략](https://www.usenix.org/conference/srecon19americas/presentation/qiu)
\* [SRE 자율성의 저주와 이를 관리하는 방법](https://www.usenix.org/conference/srecon19americas/presentation/bondi)
\* [SRE 조직 확장: 1개 팀에서 여러 팀으로의 여정](https://www.usenix.org/conference/srecon19americas/presentation/franco)
\* [SRE 교실 - 3시간 만에 분산 시스템을 설계하는 방법](https://www.usenix.org/conference/srecon19americas/presentation/thomas)
\* [PRD와 유저 여정을 활용한 사용자 친화적 도구 설계](https://www.usenix.org/conference/srecon19americas/presentation/stockman)
\* [Google SRE와 개발자가 협업하는 방식](https://www.youtube.com/watch?v=DOQqOrHs3VY)
\* [SREcon21 - SRE를 위한 실험](https://www.youtube.com/watch?v=yjusNjAFxFg)

Grab
### 블로그 포스트
\* [Our Journey to Continuous Delivery at Grab (Part 1)](https://engineering.grab.com/our-journey-to-continuous-delivery-at-grab)
\* [Our Journey to Continuous Delivery at Grab (Part 2)](https://engineering.grab.com/blog/2/)
\* [Designing Resilient Systems: Circuit Breakers or Retries? (Part 1)](https://engineering.grab.com/designing-resilient-systems-part-1)
\* [Designing Resilient Systems: Circuit Breakers or Retries? (Part 2)](https://engineering.grab.com/designing-resilient-systems-part-2)
\* [Designing Resilient Systems Beyond Retries (Part 3): Architecture Patterns and Chaos Engineering](https://engineering.grab.com/beyond-retries-part-3)
\* [Orchestrating Chaos using Grab's Experimentation Platform](https://engineering.grab.com/chaos-engineering)
\* [How We Designed the Quotas Microservice to Prevent Resource Abuse](https://engineering.grab.com/quotas-service)
\* [How We Scaled Our Cache and Got a Good Night's Sleep](https://engineering.grab.com/how-we-scaled-our-cache-and-got-a-good-nights-sleep)

Grammarly
### 블로그 포스트
\* [Scaling AWS Infrastructure to Support Multiple Regions](https://www.grammarly.com/blog/engineering/scaling-aws-infrastructure/)
\* [Security Operations in an AWS Environment](https://www.grammarly.com/blog/engineering/security-infrastructure-aws/)

Gusto
### 블로그 포스트
\* [Service Level Objectives for On-call Peace of Mind](https://engineering.gusto.com/slos-for-peace-of-mind/)
\* [Debugging Sidekiq Poison Pills](https://engineering.gusto.com/debugging-sidekiq-poison-pills/)

Halodoc
### 블로그 포스트
\* [Site Reliability Engineering for Native mobile apps](https://www.infoq.com/articles/site-reliability-engineering-mobile-apps/)

Heroku
### 블로그 포스트
\* [The Adventures of Rendezvous in Heroku’s New Architecture](https://blog.heroku.com/engineering)
\* [Incident Response at Heroku](https://blog.heroku.com/incident-response-at-heroku-2020)

IBM
### 블로그 포스트
\* [What is Site Reliability Engineering (SRE)?](https://www.ibm.com/cloud/learn/site-reliability-engineering)
\* [AIOps tools and solutions](https://www.ibm.com/cloud/aiops)

Indeed
### 블로그 포스트
\* [Indeed SRE: An Inside Look](https://engineering.indeedblog.com/blog/2022/04/sre/)
\* [Being Just Reliable Enough](https://engineering.indeedblog.com/blog/2019/10/being-just-reliable-enough/)
\* [Automating Indeed’s Release Process](https://engineering.indeedblog.com/blog/2017/03/automating-release-process/)
\* [Sloth, a Tool for Inducing Network Failures’ with Preetha Appan of Indeed.com](https://www.usenix.org/conference/srecon17americas/program/presentation/appan)
### 비디오
\* [Are We Getting Better Yet? Progress Toward Safer Operations](https://www.usenix.org/conference/srecon20americas/presentation/elman)

Indeed
### 블로그 포스트
\* [SRE Playbook - Practical Guide](https://blog.jiocinema.com/sre-playbook-practical-guide/)

Khan Academy
### 블로그 포스트
\* [How Khan Academy Successfully Handled 2.5x Traffic in a Week](https://blog.khanacademy.org/how-khan-academy-successfully-handled-2-5x-traffic-in-a-week/)
\* [Evolving our content infrastructure](https://blog.khanacademy.org/evolving-our-content-infrastructure/)

LinkedIn
### 블로그 게시물
\* [Capacity Analyzer로 사이트 용량 예측 다시 생각하기](https://engineering.linkedin.com/blog/2021/rethinking-site-capacity-projections-with-capacity-analyzer)
\* [LinkedIn의 Product SRE 팀 들여다보기](https://www.linkedin.com/pulse/insights-product-sre-team-linkedin-zaina-afoulki/?trackingId=mxKJgZ3kp8l2WI9D4UZv7Q%3D%3D)
\* [LinkedIn의 SRE 채용](https://engineering.linkedin.com/engineering-culture/hiring-sres-linkedin)
\* [오픈 소스 업데이트: School of SRE](https://engineering.linkedin.com/blog/2021/open-source-update--school-of-sre)
\* [Linux 파일 시스템 성능 회귀 현상 수정하기](https://engineering.linkedin.com/blog/2020/fixing-linux-filesystem-performance-regressions)
\* [다크 카나리를 이용한 프로덕션 테스트](https://engineering.linkedin.com/blog/2020/production-testing-with-dark-canaries)
\* [LinkedIn의 실시간 모니터링 플랫폼, ThirdEye의 스마트 알림](https://engineering.linkedin.com/blog/2019/06/smart-alerts-in-thirdeye--linkedins-real-time-monitoring-platfor)
\* [Iris 모바일: 인시던트 관리를 위한 오픈 소스 모바일 인터페이스](https://engineering.linkedin.com/blog/2019/05/iris-mobile--an-open-source--mobile-interface-for-manag)
\* [LinkedOut: 요청 수준 장애 주입 프레임워크](https://engineering.linkedin.com/blog/2018/05/linkedout--a-request-level-failure-injection-framework)
\* [완전 자동화된 부하 테스트로 반복 업무(Toil) 없애기](https://engineering.linkedin.com/blog/2019/eliminating-toil-with-fully-automated-load-testing)
\* [성공적인 지리적 분산 SRE 팀의 구성: 파트 1](https://engineering.linkedin.com/blog/2018/03/the-makeup-of-successful-geographically-distributed-sre-teams--p)
\* [성공적인 지리적 분산 SRE 팀의 구성: 파트 2](https://engineering.linkedin.com/blog/2018/03/the-makeup-of-successful-geographically-distributed-sre-teams--p0)
\* [Project STAR\*: 온콜 프로세스 간소화하기](https://engineering.linkedin.com/blog/2018/01/project-star-streamlining-our-on-call-process)
\* [온콜 자동화: Fossor 및 Ascii Etch 오픈소스화](https://engineering.linkedin.com/blog/2017/12/open-sourcing-fossor-and-ascii-etch)
\* [Project Waterbear와 함께하는 LinkedIn의 복원력 엔지니어링](https://engineering.linkedin.com/blog/2017/11/resilience-engineering-at-linkedin-with-project-waterbear)
\* [LinkedIn의 SRE 채용, 2017](https://engineering.linkedin.com/blog/2017/07/hiring-sres-at-linkedin)
\* [Iris 및 Oncall 오픈소스화](https://engineering.linkedin.com/blog/2017/06/open-sourcing-iris-and-oncall)
\* [LinkedIn의 SRE 문화 구축하기](https://engineering.linkedin.com/blog/2017/05/building-the-sre-culture-at-linkedin)
\* [실패란 없다](https://engineering.linkedin.com/blog/2017/01/failure-is-not-an-option)
\* [MTTD와 MTTR이 핵심이다](https://engineering.linkedin.com/blog/2016/12/mttd-and-mttr-are-key)
\* [측정하는 것이 개선된다](https://engineering.linkedin.com/blog/2016/12/what-gets-measured-gets-fixed)
### 동영상
\* [LinkedIn의 사이트 안정성 팀 성장시키기: 채용은 어렵다 -- Greg Leffler](https://www.youtube.com/watch?v=ZemNg9GYvOA)
\* [9년간의 실패: 형편없는 경주용 자동차를 다룬 경험이 나를 더 나은 SRE로 만든 이유](https://www.usenix.org/conference/srecon20americas/presentation/doherty)
\* [폭풍우 헤쳐나기: 조기 경보가 시스템을 구하는 방법](https://www.usenix.org/conference/srecon19emea/presentation/sherwin)
\* [언콘퍼런스: SRE의 해결되지 않은 문제들](https://www.usenix.org/conference/srecon19emea/presentation/andersen)
\* [관리하지 않고 리드하기: SRE 기술 리더 되기](https://www.usenix.org/conference/srecon19asia/presentation/palino-leading)
\* [왜 (나의) 모니터링은 구릴까?](https://www.usenix.org/conference/srecon19asia/presentation/palino-monitoring)
\* [트래픽 예측 및 인프라 스트레스 테스트](https://www.usenix.org/conference/srecon19asia/presentation/sulakhe)
\* [SRE에서 더 나은 결정을 내리기 위한 집단적 마음챙김](https

://www.usenix.org/conference/srecon19asia/presentation/andersen-mindfulness)
\* [TCP—Architecture, Enhancements, and Tuning](https://www.usenix.org/conference/srecon19asia/presentation/dhakal)
\* [Over 600 Million Members and Hundreds of Micro Services: How We Scaled Our Monitoring System to Keep up](https://www.usenix.org/conference/srecon19asia/presentation/lamba)
\* [비즈니스 지표를 이해하면 더 나은 SRE가 될 수 있는 이유](https://www.usenix.org/conference/srecon19asia/presentation/suley)
\* [Code-Yellow: 운영 중심 팀을 스마트하게 돕는 방법](https://www.usenix.org/conference/srecon19americas/presentation/kehoe)
\* [기업 간 SRE 도입 방식의 차이점](https://www.usenix.org/conference/srecon19americas/presentation/andersen)
### Tools
\* [On-Call](https://github.com/linkedin/oncall)

Loggi
### 블로그 게시물
\* [The Release Manager model](https://partiu.loggi.com/the-release-manager-model-7af93f9f499f)
\* [SRE Teams #8: Loggi](https://sreteams.substack.com/p/loggi)

Loveholidays
### 블로그 게시물
\* [Dynamic alert routing with Prometheus and Alertmanager](https://tech.loveholidays.com/dynamic-alert-routing-with-prometheus-and-alertmanager-f6a919edb5f8)
\* [Making loveholidays 18% faster with HTTP/3](https://tech.loveholidays.com/making-loveholidays-18-faster-with-http-3-1860879528a7)
\* [Enforcing best practice on self-serve infrastructure with Terraform, Atlantis and Policy As Code](https://tech.loveholidays.com/enforcing-best-practice-on-self-serve-infrastructure-with-terraform-atlantis-and-policy-as-code-911f4f8c3e00)
\* [The 5 principles that helped scale loveholidays](https://tech.loveholidays.com/the-5-principles-that-helped-scale-loveholidays-7ea0b0fd3df9)
\* [Realtime Fastly logs with Grafana Loki for under $1 a day](https://tech.loveholidays.com/realtime-fastly-logs-with-grafana-loki-for-under-1-a-day-5b63ccf32d66)

Macquarie
### 블로그 게시물
\* [Our DevSecOps journey with Golang](https://medium.com/macquarie-engineering-blog/our-devsecops-journey-with-golang-a1af38328c36)
\* [Pipeline Configuration as Code with Kotlin](https://medium.com/macquarie-engineering-blog/pipeline-configuration-as-code-with-kotlin-dec9ab9ee6fa)
\* [DevOps and Segregation of Duties](https://medium.com/macquarie-engineering-blog/devops-and-segregation-of-duties-ea4a7dcc7217)
\* [Macquarie embraces DevOps](https://medium.com/macquarie-engineering-blog/macquarie-embraces-devops-30f0fe62496a)
\* [Scaling a Kubernetes Platform across the Enterprise](https://medium.com/macquarie-engineering-blog/scaling-a-kubernetes-platform-across-the-enterprise-c07a53b6022e)

Mattermost
### 블로그 게시물
\* [Monitoring Cloud Environments at Scale with Prometheus and Thanos](https://mattermost.com/blog/monitoring-cloud-environments-at-scale-with-prometheus-and-thanos/)
\* [How We Use Sloth to do SLO Monitoring and Alerting with Prometheus](https://mattermost.com/blog/sloth-for-slo-monitoring-and-alerting-with-prometheus/)

Meituan (美团)
### 블로그 게시물
\* [The development and practice of SRE in the cloud (云端的SRE发展与实践)](https://tech.meituan.com/2017/08/03/meituanyun-sre.html)

Mercari
### 블로그 게시물
\* [Who Watches the Watchmen? Keeping an Eye on Our Monitoring Systems](https://engineering.mercari.com/en/blog/entry/20220805-who-watches-the-watchmen-keeping-an-eye-on-our-monitoring-systems/)
\* [What the Microservices SRE Team are doing as SRE Evangelists](https://engineering.mercari.com/en/blog/entry/20220225-cdb2b6deff/)
\* [What it’s like to work as an embedded microservices SRE](https://engineering.mercari.com/en/blog/entry/20220228-work-as-an-embedded-microservices-sre/)
\* [The Merpay SRE Team: Past and future](https://engineering.mercari.com/en/blog/entry/20210831-a91c3dca9d/)
\* [Embedded SRE at Mercari](https://engineering.mercari.com/en/blog/entry/20220221-embedded-sre-at-mercari/)
\* [What the SRE team wants to achieve with the development team](https://engineering.mercari.com/en/blog/entry/20210129-embedded-sre/)
\* [DevSecOps: What Is It and Why Is It Gaining Momentum in the Industry?](https://engineering.mercari.com/en/blog/entry/20201214-devsecops-what-is-it-and-why-is-it-gaining-momentum-in-the-industry/)
\* [How do we share troubleshooting skills](https://engineering.mercari.com/en/blog/entry/2020-01-28-143339/)
\* [Datadog Dashboard at Scale w / Terraform](https://engineering.mercari.com/en/blog/entry/2019-12-09-122134/)

Meta
### Blog Posts
\* [Leveraging AI for efficient incident response](https://engineering.fb.com/2024/06/24/data-infrastructure/leveraging-ai-for-efficient-incident-response/)
\* [Improving Meta’s SLO workflows with data annotations](https://engineering.fb.com/2022/08/29/developer-tools/improving-metas-slo-workflows-with-data-annotations/)
\* [SLICK: Adopting SLOs for improved reliability](https://engineering.fb.com/2021/12/13/production-engineering/slick/)
\* [More details about the October 4 outage](https://engineering.fb.com/2021/10/05/networking-traffic/outage-details/)
\* [Update about the October 4th outage](https://engineering.fb.com/2021/10/04/networking-traffic/outage/)
### Videos
\* [Scheduling at Scale: eBPF Schedulers with Sched\_ext](https://www.usenix.org/conference/srecon24emea/presentation/hodges)
\* [A Customer Service Approach to SRE](https://www.usenix.org/conference/srecon19emea/presentation/looney)
\* [How (Not) to Scale a Project: A Post-Mortem](https://www.usenix.org/conference/srecon19asia/presentation/bagnoli)
\* [Releasing the World's Largest Python Site Every 7 Minutes](https://www.usenix.org/conference/srecon19asia/presentation/wong-shuhong)
\* [Using ML to Automate Dynamic Error Categorization](https://www.usenix.org/conference/srecon19asia/presentation/davoli)

Microsoft
### Videos
\* [SLI & Reliability Deep-Dive’ with David N. Blank-Edelman of Microsoft](https://www.youtube.com/watch?v=1iMo3SkdQqQ)
\* [Ironies of Automation: A Comedy in Three Parts’ with Tanner Lund of Microsoft](https://www.youtube.com/watch?v=U3ubcoNzx9k)
\* [Sustainable Software Engineering & SREs](https://www.usenix.org/conference/srecon20americas/presentation/johnson)
\* [Study on Human Factors and Team Culture to Improve Pager Fatigue](https://www.usenix.org/conference/srecon20americas/presentation/barteneva)
\* [Prioritizing Trust While Creating Applications](https://www.usenix.org/conference/srecon19emea/presentation/davis)
\* [Building Resilience: How to Learn More from Incidents](https://www.usenix.org/conference/srecon19emea/presentation/stenning)
\* [A Tale of Two Postmortems: A Human Factors View](https://www.usenix.org/conference/srecon19asia/presentation/lund-postmortem)
\* [Availability—Thinking beyond 9s](https://www.usenix.org/conference/srecon19asia/presentation/srinivasamurthy)
\* [Ironies of Automation: A Comedy in Three Parts](https://www.usenix.org/conference/srecon19asia/presentation/lund-comedy)
\* [The Ops in Serverless](https://www.usenix.org/conference/srecon19americas/presentation/davis)

MIRO
### Blog Posts
\* [Prometheus High Availability and Fault Tolerance strategy, long term storage with VictoriaMetrics](https://medium.com/miro-engineering/prometheus-high-availability-and-fault-tolerance-strategy-long-term-storage-with-victoriametrics-82f6f3f0409e)
\* [Managing hundreds of servers for load testing: Autoscaling, custom monitoring, DevOps culture](https://medium.com/miro-engineering/managing-hundreds-of-servers-for-load-testing-autoscaling-custom-monitoring-devops-culture-390fd1c7e699)
\* [Reliable load testing with regards to unexpected nuances](https://medium.com/miro-engineering/reliable-load-testing-with-regards-to-unexpected-nuances-6f38c82196a5)

Monzo
### Blog Posts
\* [Autoscaling Monzo: How we optimise our platform to be just the right size](https://monzo.com/blog/2020/10/19/autoscaling-monzo)
\* [How we’ve evolved on-call at Monzo](https://monzo.com/blog/how-weve-evolved-on-call-at-monzo)
\* [How we respond to incidents](https://monzo.com/blog/2019/07/08/how-we-respond-to-incidents)
\* [How we monitor Monzo](https://monzo.com/blog/2018/07/27/how-we-monitor-monzo)
### Videos
\* [Eventually Consistent Service Discovery](https://www.usenix.org/conference/srecon19emea/presentation/patel)
### Tools
\* [Response](https://github.com/monzo/response)

Netflix
### 블로그 게시물
\* [Achieving observability in async workflows](https://netflixtechblog.com/achieving-observability-in-async-workflows-cd89b923c784)
\* [Building Netflix’s Distributed Tracing Infrastructure](https://netflixtechblog.com/building-netflixs-distributed-tracing-infrastructure-bb856c319304)
\* [Lessons from Building Observability Tools at Netflix](https://netflixtechblog.com/lessons-from-building-observability-tools-at-netflix-7cfafed6ab17)
\* [Edgar: Solving Mysteries Faster with Observability](https://netflixtechblog.com/edgar-solving-mysteries-faster-with-observability-e1a76302c71f)
\* [Telltale: Netflix Application Monitoring Simplified](https://netflixtechblog.com/telltale-netflix-application-monitoring-simplified-5c08bfa780ba)
\* [Keeping Customers Streaming — The Centralized Site Reliability Practice at Netflix](https://netflixtechblog.com/keeping-customers-streaming-the-centralized-site-reliability-practice-at-netflix-205cc37aa9fb)
\* [Introducing Dispatch](https://netflixtechblog.com/introducing-dispatch-da4b8a2a8072)
\* [Applying Netflix DevOps Patterns to Windows](https://netflixtechblog.com/applying-netflix-devops-patterns-to-windows-2a57f2dbbf79)
\* [ChAP: Chaos Automation Platform](https://netflixtechblog.com/chap-chaos-automation-platform-53e6d528371f)
\* [Starting the Avalanche](https://netflixtechblog.com/starting-the-avalanche-640e69b14a06)
\* [Netflix Chaos Monkey Upgraded](https://netflixtechblog.com/netflix-chaos-monkey-upgraded-1d679429be5d)
\* [Chaos Engineering Upgraded](https://netflixtechblog.com/chaos-engineering-upgraded-878d341f15fa)
\* [Automated Failure Testing](https://netflixtechblog.com/automated-failure-testing-86c1b8bc841f)
\* [From Chaos to Control — Testing the resiliency of Netflix’s Content Discovery Platform](https://netflixtechblog.com/from-chaos-to-control-testing-the-resiliency-of-netflixs-content-discovery-platform-ce5566aef0a4)
\* [Introducing Atlas: Netflix’s Primary Telemetry Platform](https://netflixtechblog.com/introducing-atlas-netflixs-primary-telemetry-platform-bd31f4d8ed9a)
\* [FIT: Failure Injection Testing](https://netflixtechblog.com/fit-failure-injection-testing-35d8e2a9bb2)
\* [Announcing Security Monkey — AWS Security Configuration Monitoring and Analysis](https://netflixtechblog.com/announcing-security-monkey-aws-security-configuration-monitoring-and-analysis-1f2bfb001708)
\* [Lessons Netflix Learned from the AWS Outage](https://netflixtechblog.com/lessons-netflix-learned-from-the-aws-outage-deefe5fd0c04)
\* [Scryer: Netflix’s Predictive Auto Scaling Engine](https://netflixtechblog.com/scryer-netflixs-predictive-auto-scaling-engine-a3f8fc922270)
### 주요 장애 및 분석 보고서
\* [Post-mortem of October 22, 2012 AWS degradation](https://netflixtechblog.com/post-mortem-of-october-22-2012-aws-degradation-efcee3ab40d5)
### 동영상
\* [Achieving Excellence: SLO Thresholds That Transform Service Quality](https://www.usenix.org/conference/srecon24emea/presentation/ortiz)
\* [AWS re:Invent 2019: A day in the life of a Netflix engineer (NFX202)](https://www.youtube.com/watch?v=0QS1TWLooo0)
\* [When /bin/sh Attacks: Revisiting "Automate All the Things"](https://www.usenix.org/conference/srecon20americas/presentation/reed)
\* [How Did Things Go Right? Learning More from Incidents](https://www.usenix.org/conference/srecon19americas/presentation/kitchens)
\* [Monitoring and Tracing @Netflix Streaming Data Infrastructure](https://www.youtube.com/watch?v=DlWYNoLmma8)
\* [Real user performance monitoring at Netflix scale ‐ Martin Spier](https://www.youtube.com/watch?v=4RG2DUK03\_0)
\* [AWS re:Invent 2017 - Nora Jones Describes Why We Need More Chaos - Chaos Engineering, That Is](https://www.youtube.com/watch?v=rgfww8tLM0A)
\* [AWS re:Invent 2017: Performing Chaos at Netflix Scale (DEV334)](https://www.youtube.com/watch?v=LaKGx0dAUlo)
\* [Netflix: Multi-Regional Resiliency and Amazon Route 53](https://www.youtube.com/watch?v=WDDkLOT8SCk)
\* [Designing Service

s for Resilience: Netflix Lessons](https://www.youtube.com/watch?v=RWyZkNzvC-c)
\* [South Bay SRE Meetup - Netflix Cloud Performance Team](https://www.youtube.com/watch?v=uQ0flQOtQEA)
\* [AWS re:Invent 2017: A Day in the Life of a Netflix Engineer III (ARC209)](https://www.youtube.com/watch?v=T\_D1G42G0dE)
\* [How Netflix Uses Kinesis Streams to Monitor Applications and Analyze Billions of Traffic Flows](https://www.youtube.com/watch?v=8tsIqfvizpU)
\* [Mastering Chaos - A Netflix Guide to Microservices](https://www.youtube.com/watch?v=CZ3wIuvmHeM)
\* [AWS re:Invent 2016: From Resilience to Ubiquity - #NetflixEverywhere Global Architecture (ARC204)](https://www.youtube.com/watch?v=leqUbSY55hY)
\* [SREcon 2016 - Netflix: 190 Countries and 5 CORE SREs](https://www.youtube.com/watch?v=koGaH4ffXaU)
\* [From Sys Admin to Netflix SRE](https://www.youtube.com/watch?v=lZI51YzIgVE)
\* [Application Resilience Engineering and Operations at Netflix with Hystrix](https://www.youtube.com/watch?v=RzlluokGi1w)
\* [Injecting Failure at Netflix](https://www.youtube.com/watch?v=ioXV28GtXeo)
\* [LISA13 - How Netflix Embraces Failure to Improve Resilience and Maximize Availability](https://www.youtube.com/watch?v=3D0zS3kPNUU)
\* [Incident Management at Netflix Velocity](https://www.infoq.com/presentations/netflix-incident-management/)
### 팟캐스트
\* [Ryan Kitchens on Learning from Incidents at Netflix, the Role of SRE, and Sociotechnical Systems](https://www.infoq.com/podcasts/netflix-sre-sociotechnical-systems/)
### 도구
\* [Dispatch](https://github.com/Netflix/dispatch)

New Relic
### 블로그 포스트
\* [Defining Modern Software Roles: SREs at New Relic](https://newrelic.com/blog/nerd-life/new-relic-sre)
\* [10 Things Everybody Needs to Know About Site Reliability Engineering (SRE)](https://newrelic.com/blog/best-practices/site-reliability-engineering-careers)
\* [What Tools Do Site Reliability Engineers Use?](https://newrelic.com/blog/best-practices/best-sre-tools)
\* [A Day in the Life of a New Relic SRE](https://newrelic.com/blog/nerd-life/what-does-an-sre-do)
\* [7 Habits of Highly Successful Site Reliability Engineers](https://newrelic.com/blog/best-practices/site-reliability-engineer-sre-habits)
\* [Adopting the practice of SRE](https://newrelic.com/blog/best-practices/adopting-sre-practices)
\* [Using modern observability to establish a data-driven culture](https://newrelic.com/blog/best-practices/observability-data-driven-culture)

Nubank
### 블로그 포스트
\* [Engineering operational excellence, a case of continuous improvement](https://building.nubank.com.br/engineering-operational-excellence-case-continuous-improvement/)
\* [How we deal with technical incidents](https://building.nubank.com.br/how-we-deal-with-incidents/)
\* [How we do On-Call Rotations at Nubank](https://building.nubank.com.br/how-we-do-on-call-rotations-at-nubank/)
\* [How we scale our data platform efficiently and reliably](https://building.nubank.com.br/distributing-the-data-team-to-boost-innovation-reliably/)
\* [Why We Killed Our End-to-End Test Suite](https://building.nubank.com.br/why-we-killed-our-end-to-end-test-suite/)
\* [Automatic retraining for machine learning models: tips and lessons learned](https://building.nubank.com.br/automatic-retraining-for-machine-learning-models/)

OpenAI
### 블로그 포스트
\* [March 20 ChatGPT outage: Here’s what happened](https://openai.com/blog/march-20-chatgpt-outage)
\* [OpenAI SRE and scaling explained easy.](https://medium.com/@Pran-Ker/openai-sre-miracle-19a33bdd3145)
\* [Scaling Kubernetes to 2,500 nodes](https://openai.com/research/scaling-kubernetes-to-2500-nodes)
\* [Scaling Kubernetes to 7,500 nodes](https://openai.com/research/scaling-kubernetes-to-7500-nodes)
\* [Scaling AI Infrastructure at OpenAI](https://www.youtube.com/watch?v=cK7qFZ9J6k0)

PayPal
### 블로그 포스트
\* [Triggered: Incident #1234 (incident process needs fixing)](https://medium.com/paypal-tech/triggered-incident-1234-incident-process-needs-fixing-2a09dbac9edd)
\* [Implementing Observability in a Service Mesh](https://medium.com/paypal-tech/implementing-observability-in-a-service-mesh-273c7409283d)
\* [PostgreSQL at Scale: Database Schema Changes Without Downtime](https://medium.com/paypal-tech/postgresql-at-scale-database-schema-changes-without-downtime-20d3749ed680)
\* [Scaling GraphQL at PayPal](https://medium.com/paypal-tech/scaling-graphql-at-paypal-b5b5ac098810)
### 동영상
\* [SREcon Conversations Asia/Pacific with Karthikeyan Selvaraj and Rajesh Ramachandran, PayPal](https://www.youtube.com/watch?v=XAIj567wBsU&feature=emb\_title)
\* [SRE Then vs SRE Now: A Balancing Act between Reflexes and Intuitive Instincts at PayPal](https://www.usenix.org/conference/srecon19asia/presentation/sunder-vr)
\* [Detecting Service Degradation and Failures at Scale through Distributed Log Processing](https://www.usenix.org/conference/srecon19asia/presentation/narayanan)
\* [Operating Elasticsearch with Ease at Scale](https://www.usenix.org/conference/srecon19asia/presentation/sankaravadivel)
\* [Ensuring Site Reliability through Security Controls](https://www.usenix.org/conference/srecon19asia/presentation/janakiraman)

Picnic
### 블로그 포스트
\* [Micrometer and the Modern Observability Stack](https://blog.picnic.nl/micrometer-and-the-modern-observability-stack-ebf72283bd8e)
\* [Monitoring and Observability at Picnic](https://blog.picnic.nl/monitoring-and-observability-at-picnic-684cefd845c4)

Pinterest
### 블로그 게시물
\* [Ensuring High Availability of Ads Realtime Streaming Services](https://medium.com/pinterest-engineering/ensuring-high-availability-of-ads-realtime-streaming-services-ea3889420490)
\* [Improving efficiency and reducing runtime using S3 read optimization](https://medium.com/pinterest-engineering/improving-efficiency-and-reducing-runtime-using-s3-read-optimization-b31da4b60fa0)
\* [Scaling Kubernetes with Assurance at Pinterest](https://medium.com/pinterest-engineering/scaling-kubernetes-with-assurance-at-pinterest-a23f821168da)
\* [What we learned from an iOS app OOMs incident](https://medium.com/pinterest-engineering/what-we-learned-from-an-ios-app-ooms-incident-eb31eada251)
\* [How we designed our Continuous Integration System to be more than 50% Faster](https://medium.com/pinterest-engineering/how-we-designed-our-continuous-integration-system-to-be-more-than-50-faster-b70a59342fe2)
\* [Simplifying web deploys](https://medium.com/pinterest-engineering/simplifying-web-deploys-19244fe13737)
\* [Upgrading Pinterest operational metrics](https://medium.com/pinterest-engineering/upgrading-pinterest-operational-metrics-8718d058079a)
\* [Distributed tracing at Pinterest with new open source tools](https://medium.com/pinterest-engineering/distributed-tracing-at-pinterest-with-new-open-source-tools-a4f8a5562f6b)
\* [Auto scaling Pinterest](https://medium.com/pinterest-engineering/auto-scaling-pinterest-df1d2beb4d64)
### 동영상
\* [Building Actionable Code Ownership](https://www.usenix.org/conference/srecon20americas/presentation/mukherji)
\* [Evolution of Observability Tools at Pinterest](https://www.usenix.org/conference/srecon19emea/presentation/abbas)
\* [Automating OS/Platform Upgrades for Service Owners](https://www.usenix.org/conference/srecon19asia/presentation/menezes)

Postman
### 블로그 게시물
\* [Learn how your Kubernetes clusters respond to failure using Gremlin and Grafana](https://medium.com/better-practices/chaos-d3ef238ec328)

Prezi
### 블로그 게시물
\* [How to avoid global outage — Seamlessly migrating DaemonSet labels](https://engineering.prezi.com/intro-4727024fc2c1)
\* [In search of speed — debugging Elasticsearch performance](https://engineering.prezi.com/in-search-of-speed-debugging-elasticsearch-performance-9ce8edf4af40)
\* [Prometheus at Prezi: replacing 10 years of anti-patterns](https://engineering.prezi.com/prometheus-at-prezi-replacing-10-years-of-anti-patterns-e3c2317e6ca)

Red Hat
### 블로그 게시물
\* [From Ops to SRE: Evolution of the OpenShift Dedicated Team](https://www.openshift.com/blog/from-ops-to-sre-evolution-of-the-openshift-dedicated-team)
\* [5 Agile Practices Every SRE Team Should Adopt](https://www.openshift.com/blog/5-agile-practices-every-sre-team-should-adopt)
\* [7 Best Practices for Writing Kubernetes Operators: An SRE Perspective](https://www.openshift.com/blog/7-best-practices-for-writing-kubernetes-operators-an-sre-perspective)

Reddit
### 동영상
\* [Noisy Neighbors, through Networking](https://www.usenix.org/conference/srecon24emea/presentation/treffer)

Riot Games
### Blog Posts
\* [THE LEGENDS OF RUNETERRA CI/CD PIPELINE](https://technology.riotgames.com/news/legends-runeterra-cicd-pipeline)
\* [STRATEGIES FOR WORKING IN UNCERTAIN SYSTEMS](https://technology.riotgames.com/news/strategies-working-uncertain-systems)
\* [IMPROVING THE DEVELOPER EXPERIENCE FOR OPERATING SERVICES](https://technology.riotgames.com/news/improving-developer-experience-operating-services)
\* [SCALABILITY AND LOAD TESTING FOR VALORANT](https://technology.riotgames.com/news/scalability-and-load-testing-valorant)
\* [LEVERAGING GOLANG FOR GAME DEVELOPMENT AND OPERATIONS](https://technology.riotgames.com/news/leveraging-golang-game-development-and-operations)
\* [CONTROLLED CHAOS WITH FAULT INJECTION TESTING](https://technology.riotgames.com/)
\* [DOWN THE RABBIT HOLE OF PERFORMANCE MONITORING](https://technology.riotgames.com/news/down-rabbit-hole-performance-monitoring)
\* [PROFILING: THE CASE OF THE MISSING MILLISECONDS](https://technology.riotgames.com/news/profiling-case-missing-milliseconds)
\* [PROFILING: REAL WORLD PERFORMANCE IN LEAGUE](https://technology.riotgames.com/news/profiling-real-world-performance-league)
\* [PROFILING: OPTIMISATION](https://technology.riotgames.com/news/profiling-optimisation)
\* [PROFILING: MEASUREMENT AND ANALYSIS](https://technology.riotgames.com/news/profiling-measurement-and-analysis)
\* [RUNNING ONLINE SERVICES AT RIOT: PART I](https://technology.riotgames.com/news/running-online-services-riot-part-i)
\* [RUNNING ONLINE SERVICES AT RIOT: PART II](https://technology.riotgames.com/news/running-online-services-riot-part-ii)
\* [RUNNING ONLINE SERVICES AT RIOT: PART III](https://technology.riotgames.com/news/running-online-services-riot-part-iii)
\* [RUNNING ONLINE SERVICES AT RIOT: PART III: PART DEUX](https://technology.riotgames.com/news/running-online-services-riot-part-iii-part-deux)
\* [RUNNING ONLINE SERVICES AT RIOT: PART IV](https://technology.riotgames.com/news/running-online-services-riot-part-iv)
\* [RUNNING ONLINE SERVICES AT RIOT: PART V](https://technology.riotgames.com/news/running-online-services-riot-part-v)
\* [THE EVOLUTION OF SECURITY AT RIOT](https://technology.riotgames.com/news/evolution-security-riot)
\* [RUNNING AN AUTOMATED TEST PIPELINE FOR THE LEAGUE CLIENT UPDATE](https://technology.riotgames.com/news/running-automated-test-pipeline-league-client-update)
\* [AUTOMATED TESTING FOR LEAGUE OF LEGENDS](https://technology.riotgames.com/news/automated-testing-league-legends)
### Videos
\* [Riot Games: Evolution of Observability at the Gaming Company](https://www.usenix.org/conference/srecon24emea/presentation/moreira)

Salesforce
### 블로그 글
\* [멀티 테넌시를 위한 Kubernetes Control Plane 살펴보기](https://engineering.salesforce.com/looking-at-the-kubernetes-control-plane-for-multi-tenancy-88914cd7aa89)
\* [대규모 트래픽을 위한 EKS 네트워킹 최적화](https://engineering.salesforce.com/optimizing-eks-networking-for-scale-1325706c8f6d)
\* [Kubernetes 클러스터에서 다운타임 없는 노드 패치 적용하기](https://engineering.salesforce.com/zero-downtime-node-patching-in-a-kubernetes-cluster-cdceb21c8c8c)
\* [이유(Why)가 아닌 방법(How)에 집중하기: 포스트모템을 위한 5Whys의 대안](https://engineering.salesforce.com/how-not-why-an-alternative-to-the-five-whys-for-post-mortems-4518098cca17)
\* [Kubernetes를 위한 제네릭 Sidecar Injector](https://engineering.salesforce.com/a-generic-sidecar-injector-for-kubernetes-c05eede1f6bb)
\* [마이크로서비스 기반 제품을 위한 모니터링 전략 구현](https://engineering.salesforce.com/implementation-of-a-monitoring-strategy-for-products-based-microservices-24ad24c4c3e5)
\* [실제로 '쓰게 될' 장애 대응 계획을 수립하는 10가지 단계](https://engineering.salesforce.com/10-steps-to-develop-an-incident-response-plan-youll-actually-use-6cc49d9bf94c)
\* [완벽에 가까운 로그 파이프라인을 구축하기 위한 여정](https://engineering.salesforce.com/our-journey-to-a-near-perfect-log-pipeline-6ae2f80cf7a0)
\* [Web Workers를 활용한 성능 최적화](https://engineering.salesforce.com/optimizing-performance-with-web-workers-612b48621d8d)
\* [잠시 숨을 고르고 집중하기](https://engineering.salesforce.com/take-a-moment-to-refocus-86b6546c90c)

Schibsted Media
### 블로그 글
\* [스칸디나비아 상위 10위권 사이트를 위한 신뢰성 엔지니어링](https://alexewerlof.medium.com/reliability-engineering-for-some-of-top-10-sites-in-scandinavia-91e388d8d13a)

Scribd
### 블로그 글
\* [장애로부터 배우기: Sidekiq이 10억 건의 작업을 처리할 수 있도록 준비하기](https://tech.scribd.com/blog/2020/sidekiq-incident-learnings.html)
\* [Scribd에서의 PagerDuty 사용 후기](https://tech.scribd.com/blog/2020/pagerduty-at-scribd.html)
\* [개발자에게 PagerDuty 당직 할당하기](https://tech.scribd.com/blog/2019/managing-pagerduty-rotations.html)

Shopify
### 블로그 글
\* [대규모 트래픽 이벤트를 위한 복원력(Resiliency) 계획 수립](https://shopify.engineering/resiliency-planning-for-high-traffic-events)
\* [대규모 환경에서의 용량 산정(Capacity Planning)](https://shopify.engineering/capacity-planning-shopify)
\* [DNS 트래픽 관리를 활용하여 Shopify 서비스에 복원력 더하기](https://shopify.engineering/using-dns-traffic-management-add-resiliency-shopify-services)
\* [효과적인 Game Day 테스트를 만들기 위한 4단계](https://shopify.engineering/four-steps-creating-effective-game-day-tests)
\* [장애 관리 절차에 ChatOps 도입하기](https://shopify.engineering/implementing-chatops-into-our-incident-management-procedure)
\* [Shopify의 StatsD](https://shopify.engineering/17488320-statsd-at-shopify)
### 동영상
\* [Elasticsearch 성능 향상: 전용 노드와 KEDA 오토스케일러를 활용한 혁신적인 재색인 전략](https://www.usenix.org/conference/srecon24emea/presentation/vayghan)
\* [네트워크 모니터: 관측 가능성(Observability)의 공백을 인지하게 된 이야기](https://www.usenix.org/conference/srecon19emea/presentation/gedge)
\* [예기치 못한 상황에 대비하기: 새로운 유형의 장애 대응을 위한 SRE 팀 준비시키기](https://www.usenix.org/conference/srecon19emea/presentation/arthorne)
\* [고급 냅킨 수학: 제1원칙을 통한 시스템 성능 추정](https://www.usenix.org/conference/srecon19emea/presentation/eskildsen)

Sky Betting and Gaming
### Blog Posts
\* [It’s Just a Monitoring Change](https://sbg.technology/2020/12/09/its-just-a-monitoring-change/)
\* [“What's the worst that could happen?”: A worked example of how we deal with live incidents](https://sbg.technology/2020/04/02/whats-the-worst-that-can-happen/)
\* [Rising from the Ashes](https://sbg.technology/2020/02/07/rising-from-the-ashes/)
\* [Crash! Bang! Wallop! Practice makes perfect](https://sbg.technology/2018/05/04/firedrills-in-core/)
\* [Performance Left Right and Center](https://sbg.technology/2017/10/23/performance-left-right-and-center/)

Slack
### Blog Posts
\* [Slack’s Incident on 2-22-22](https://slack.engineering/slacks-incident-on-2-22-22/)
\* [Infrastructure Observability for Changing the Spend Curve](https://slack.engineering/infrastructure-observability-for-changing-the-spend-curve/)
\* [Slack’s Outage on January 4th 2021](https://slack.engineering/slacks-outage-on-january-4th-2021/)
\* [A Terrible, Horrible, No-Good, Very Bad Day at Slack](https://slack.engineering/a-terrible-horrible-no-good-very-bad-day-at-slack/)
\* [Deploys at Slack](https://slack.engineering/deploys-at-slack/)
\* [Disasterpiece Theater: Slack’s process for approachable Chaos Engineering](https://slack.engineering/disasterpiece-theater-slacks-process-for-approachable-chaos-engineering/)
### Videos
\* [Scaling Chef Emotionally](https://www.usenix.org/conference/srecon23emea/presentation/pemberton)
\* [Slack at the Edge](https://www.usenix.org/conference/srecon19asia/presentation/pemberton)
\* [What Breaks Our Systems: A Taxonomy of Black Swans](https://www.usenix.org/conference/srecon19americas/presentation/nolan-taxonomy)

Slalom Build
### Blog Posts
\* [How to Implement Service Level Objectives in New Relic APM](https://medium.com/slalom-build/how-to-implement-service-level-objectives-in-new-relic-apm-f34f8746118b)
\* [Beginners Guide to DevOps: How to Make It into the Industry](https://medium.com/slalom-build/beginners-guid-to-devops-how-to-make-it-into-the-industry-c1652d59807)
\* [GitHub Actions: Beyond CI/CD](https://medium.com/slalom-build/github-actions-beyond-ci-cd-cb3ddc6abaa)
\* [Why isn’t all test automation run on the pipeline?](https://medium.com/slalom-build/why-isnt-all-test-automation-run-on-the-pipeline-b2c57afbdf5a)
\* [The Many Shapes of Site Reliability Engineering](https://medium.com/slalom-build/the-many-shapes-of-site-reliability-engineering-468359866517)
\* [How to build a secure by default Kubernetes cluster with a basic CI/CD pipeline on AWS](https://medium.com/slalom-build/how-to-build-a-secure-by-default-kubernetes-cluster-with-a-basic-ci-cd-pipeline-on-aws-ebfe0da1c7c9)
\* [Secret Management Architectures: Finding the balance between security and complexity](https://medium.com/slalom-build/secret-management-architectures-finding-the-balance-between-security-and-complexity-d857ceaa2300)
\* [Detecting Malicious Requests with Keras & Tensorflow](https://medium.com/slalom-build/detecting-malicious-requests-with-keras-tensorflow-5d5db06b4f28)
\* [The Lego Monolith — A Monolith Microservice Proof of Concept](https://medium.com/slalom-build/the-lego-monolith-a-monolith-microservice-proof-of-concept-a402ca1654e4)
\* [Managing Secrets Using Hashicorp Vault](https://medium.com/slalom-build/managing-secrets-using-hashicorp-vault-ed6b9e0375ac)
\* [Packaging Spring Boot Applications for Deployment on Kubernetes](https://medium.com/slalom-build/packaging-spring-boot-applications-for-deployment-on-kubernetes-5fb64bc65406)
\* [Immutable Infrastructure and Continuous Delivery in the Cloud](https://medium.com/slalom-build/immutable-infrastructure-and-continuous-delivery-in-the-cloud-56ee4b31b8d5)

Soundcloud
### 블로그 글
\* [시스템을 성공적으로 인수인계하는 방법](https://developers.soundcloud.com/blog/how-to-successfully-hand-over-systems)
\* [건전한 온콜(On-Call) 문화 구축하기](https://developers.soundcloud.com/blog/building-a-healthy-on-call-culture)
\* [프로처럼 SLO 알럿 설정하기](https://developers.soundcloud.com/blog/alerting-on-slos)
\* [Canary를 활용한 핸즈오프 배포](https://developers.soundcloud.com/blog/hands-off-deployment-with-canary)
\* [성숙해진 Prometheus – 오픈소스 프로젝트의 발전에 대한 소고](https://developers.soundcloud.com/blog/prometheus-has-come-of-age-a-reflection-on-the-development-of-an-open-source-project)
\* [Prometheus: Soundcloud의 모니터링](https://developers.soundcloud.com/blog/prometheus-monitoring-at-soundcloud)
\* [SRE 연수생으로서 1년 동안 배운 것들](https://developers.soundcloud.com/blog/sre-trainee)
\* [확대경으로 살펴본 테스트](https://developers.soundcloud.com/blog/tests-under-the-magnifying-lens)

Spotify
### 블로그 글
\* [Matt Clarke: 시니어 백엔드 인프라 엔지니어](https://engineering.atspotify.com/2021/03/09/my-beat-matt-clarke/)
\* [개발자를 위한 더 나은 Kubernetes 경험 설계하기](https://engineering.atspotify.com/2021/03/01/designing-a-better-kubernetes-experience-for-developers/)
\* [테크바이트: 업계가 장애에 대해 놓치고 있는 점과 대처 방안](https://engineering.atspotify.com/2020/02/26/techbytes-what-the-industry-misses-about-incidents-and-what-you-can-do/)
\* [GCP에서의 자동화된 장애 대응 인프라](https://engineering.atspotify.com/2019/04/04/whacking-a-million-moles-automated-incident-response-infrastructure-in-gcp/)
### 동영상
\* [빠르고 느린 트레이싱: 웹 서비스 성능 파헤치고 개선하기](https://www.usenix.org/conference/srecon19americas/presentation/root)

Squarespace
### 블로그 글
\* [후면 들여다보기: 사이트 신뢰성 보장하기](https://engineering.squarespace.com/blog/2017/under-the-hood-ensuring-site-reliability)
### 동영상
\* [마찰 뚫고 나아가기](https://www.usenix.org/conference/srecon19emea/presentation/na)
\* [이미 불타고 있을 때 SRE를 수행하는 방법](https://www.usenix.org/conference/srecon19emea/presentation/hidalgo)
\* [사례 연구: 신규 서비스를 위한 SLO 구현하기](https://www.usenix.org/conference/srecon19americas/presentation/lawson)
\* [코드 리뷰 문화 조성하기](https://www.usenix.org/conference/srecon19americas/presentation/turner)

Stack Overflow
### 블로그 글
\* [“이런 일은 절대 일어나지 않아야 합니다. 만약 일어난다면 개발자를 호출하세요.”](https://stackoverflow.blog/2021/03/18/creating-a-good-feedback-loop-between-ops-and-devs-using-documentation/)
\* [코드로서의 인프라: 몇 초 만에 인프라 요소 생성 및 구성하기](https://stackoverflow.blog/2021/03/08/infrastructure-as-code-create-and-configure-infrastructure-elements-in-seconds/)
\* [CI/CD의 약속 실현하기](https://stackoverflow.blog/2021/01/19/fulfilling-the-promise-of-ci-cd/)
\* [2019년 5월 보안 인시던트 심층 분석](https://stackoverflow.blog/2021/01/25/a-deeper-dive-into-our-may-2019-security-incident/)
\* [게스트 포스트 - 무너지지 않고 장애 조치(Failover) 수행하기](https://stackoverflow.blog/2020/10/23/adrian-cockcroft-aws-failover-chaos-engineering-fault-tolerance-distaster-recovery/)
\* [블로그를 구축한 방법](https://stackoverflow.blog/2015/07/02/how-we-built-our-blog/)
\* [Netlify를 통해 엔지니어링 시간을 절약한 Stack Overflow](https://www.netlify.com/blog/stack-overflow-case-study/)
### 동영상
\* [저컨텍스트 데브옵스: 기본값, 문서화, 규율을 통한 SRE 팀 문화 개선](https://www.usenix.org/conference/srecon20americas/presentation/limoncelli)

Strava
### 블로그 게시물
\* [Scaling Club Leaderboard Infrastructure for Millions of Users](https://medium.com/strava-engineering/scaling-club-leaderboard-infrastructure-for-millions-of-users-9ee857ce8cfe)
\* [Distributed Tracing at Strava](https://medium.com/strava-engineering/distributed-tracing-at-strava-e9d784b9ddf2)

Stripe
### 블로그 게시물
\* [Fast and flexible observability with canonical log lines](https://stripe.com/blog/canonical-log-lines)
\* [Fast builds, secure builds. Choose two.](https://stripe.com/blog/fast-secure-builds-choose-two)
\* [Introducing Veneur: high performance and global aggregation for Datadog](https://stripe.com/blog/introducing-veneur-high-performance-and-global-aggregation-for-datadog)
### 동영상
\* [How Stripe Invests in Technical Infrastructure](https://www.usenix.org/conference/srecon19emea/presentation/larson)
\* [The AWS Billing Machine and Optimizing Cloud Costs](https://www.usenix.org/conference/srecon19asia/presentation/lopopolo)

Target
### 블로그 게시물
\* [Ɔhaos Ǝnginǝǝring @ Target - Part 2](https://tech.target.com/2019/05/09/chaos-engineering-at-Target.html)
\* [Ɔhaos Ǝnginǝǝring @ Target - Part 1](https://tech.target.com/2019/02/05/chaos-engineering-at-Target.html)
\* [GoAlert - Your Future Open Source, On-Call Notification Product](https://tech.target.com/2019/02/25/introducing-goalert.html)

Teads
### 블로그 게시물
\* [Scaling your on-duty team](https://medium.com/teads-engineering/scaling-your-on-duty-team-bc467c480747)

Tinder
### 블로그 게시물
\* [The Ultimate Load Test](https://medium.com/tinder-engineering/the-ultimate-load-test-c32b37adc11b)
\* [How We Improved Our Performance Using ElasticSearch Plugins: Part 1](https://medium.com/tinder-engineering/how-we-improved-our-performance-using-elasticsearch-plugins-part-1-b0850a7e5224)
\* [How We Improved Our Performance Using ElasticSearch Plugins: Part 2](https://medium.com/tinder-engineering/how-we-improved-our-performance-using-elasticsearch-plugins-part-2-b051da2ee85b)
\* [Tinder’s move to Kubernetes](https://medium.com/tinder-engineering/tinders-move-to-kubernetes-cda2a6372f44)

Tokopedia
### 블로그 게시물
\* [Benefits of benchmarking with Go](https://medium.com/tokopedia-engineering/benefits-of-benchmarking-with-go-f8bfa177f7fa)
\* [Simulating Customized Chaos in Golang using Toxiproxy](https://medium.com/tokopedia-engineering/simulating-customized-chaos-in-golang-using-toxiproxy-b913584d88a7)
\* [How Tokopedia Rank Millions of Products in Search Page](https://medium.com/tokopedia-engineering/how-tokopedia-rank-millions-of-products-in-search-page-70e358ea2274)

Trivago
### 블로그 게시물
\* [How To Get Fooled By Metrics](https://tech.trivago.com/2020/12/04/how-to-get-fooled-by-metrics/)

Twilio
### 블로그 게시물
\* [Twilio SRE Gameday Template](https://github.com/twilio/gameday/blob/main/get\_to\_know\_your\_systems.md)

Twitter
### 블로그 게시물
\* [Logging at Twitter: Updated](https://blog.twitter.com/engineering/en\_us/topics/infrastructure/2021/logging-at-twitter-updated)
\* [Deleting data distributed throughout your microservices architecture](https://blog.twitter.com/engineering/en\_us/topics/infrastructure/2020/deleting-data-distributed-throughout-your-microservices-architecture)
\* [Deterministic Aperture: A distributed, load balancing algorithm](https://blog.twitter.com/engineering/en\_us/topics/infrastructure/2019/daperture-load-balancer)
\* [MetricsDB: TimeSeries Database for storing metrics at Twitter](https://blog.twitter.com/engineering/en\_us/topics/infrastructure/2019/metricsdb)
\* [The Infrastructure Behind Twitter: Scale](https://blog.twitter.com/engineering/en\_us/topics/infrastructure/2017/the-infrastructure-behind-twitter-scale)
\* [The infrastructure behind Twitter: efficiency and optimization](https://blog.twitter.com/engineering/en\_us/topics/infrastructure/2016/the-infrastructure-behind-twitter-efficiency-and-optimization)

Uber
### Blog Posts
\* [Founding Uber SRE](https://lethain.com/founding-uber-sre/)
\* [Disaster Recovery for Multi-Region Kafka at Uber](https://eng.uber.com/kafka/)
\* [Engineering Failover Handling in Uber’s Mobile Networking Infrastructure](https://eng.uber.com/eng-failover-handling/)
\* [Optimizing Observability with Jaeger, M3, and XYS at Uber](https://eng.uber.com/optimizing-observability/)
### Videos
\* [A Tale of Two Rotations: Building a Humane & Effective On-Call](https://www.usenix.org/conference/srecon19emea/presentation/lee)
\* [Testing in Production at Scale](https://www.usenix.org/conference/srecon19americas/presentation/gud)
\* [A History of SRE at Uber’ with Rick Boone of Uber](https://www.youtube.com/watch?v=qJnS-EfIIIE)

Udemy
### Blog Posts
\* [Blameless Incident Reviews at Udemy](https://medium.com/udemy-engineering/blameless-incident-reviews-at-udemy-aa4773dbaf0b)
\* [How Udemy does Build Engineering](https://medium.com/udemy-engineering/how-udemy-does-build-engineering-9722e98a4208)
### Videos
\* [Monitoring Systems as a Service – Walking the Line between Giving Your Devs Good M&O and Setting All Your Money on Fire](https://www.usenix.org/conference/srecon24emea/presentation/ocallaghan)
\* [Udemy - How to Do SRE When You Have No SRE](https://www.usenix.org/conference/srecon19emea/presentation/ocallaghan)

upGrad
### Blog Posts
\* [Web Performance and Related Stories — upgrad.com](https://engineering.upgrad.com/web-performance-and-related-stories-upgrad-com-a9fb9c6bb766)
\* [Beginner’s guide to web analytics](https://engineering.upgrad.com/beginners-guide-to-analytics-c8ce3e92fa42)
\* [iOS Continuous Deployment with Bitbucket, Jenkins and Fastlane at UpGrad](https://engineering.upgrad.com/ios-continuous-deployment-with-bitbucket-jenkins-and-fastlane-at-upgrad-699b3b48acca)

VGW
### Blog Posts
\* [The SRE Incident Response game](https://medium.com/@bruce\_25864/the-sre-incident-response-game-db242fff391c)
### Videos
\* [Level Up Your Incident Response With Gameplay](https://youtu.be/c2-52EP8\_7c)

Wikimedia Foundation
### Videos
\* [Testing Encyclopedias in Production](https://www.usenix.org/conference/srecon20americas/presentation/mouzeli)
\* [What Happens When You Type en.wikipedia.org?](https://www.usenix.org/conference/srecon19emea/presentation/mouzeli)

Wix
### Blog Posts
\* [How We Improved Website Performance by Evolving Our Infrastructure](https://www.wix.engineering/post/how-we-improved-website-performance-by-evolving-our-infrastructure)
\* [Wix Inbox Journey: 3 Approaches for Zero Downtime Database Migration](https://www.wix.engineering/post/wix-inbox-journey-3-approaches-for-zero-downtime-database-migration)
\* [Moving Velo to Multiple Container Sites: The Why, The How and The Lessons Learned](https://www.wix.engineering/post/moving-velo-to-multiple-container-sites-the-why-the-how-and-the-lessons-learned)
\* [Making Order in CI/CD Mess](https://www.wix.engineering/post/making-order-in-ci-cd-mess)

Yelp
### Blog Posts
\* [The process: Implementing Yelp’s failover strategy](https://increment.com/reliability/yelp-traffic-failover-strategy/)
### Videos
\* [Yelp - What I Wish I Knew before Going On-Call](https://www.usenix.org/conference/srecon19emea/presentation/shu)

Zalando
### Blog Posts
\* [Tracing SRE’s journey in Zalando - Part I](https://engineering.zalando.com/posts/2021/09/sre-journey-part1.html)
\* [Tracing SRE’s journey in Zalando - Part II](https://engineering.zalando.com/posts/2021/09/sre-journey-part2.html)
\* [Tracing SRE’s journey in Zalando - Part III](https://engineering.zalando.com/posts/2021/10/sre-journey-part3.html)
### Vidoes
\* [The Frontiers of Reliability Engineering](https://www.usenix.org/conference/srecon24emea/presentation/hartmann)
\* [Service Level Objectives](https://www.usenix.org/conference/srecon24emea/presentation/discussion-slos)

Zerodha
### Blog Posts
\* [Infrastructure monitoring with Prometheus at Zerodha](https://zerodha.tech/blog/infra-monitoring-at-zerodha/)
\* [Logging at Zerodha](https://zerodha.tech/blog/logging-at-zerodha/)

Zomato
### 블로그 게시물
\* [Huddle Diaries – DevOps and Data Platform](https://www.zomato.com/blog/huddle-diaries-devops-and-data-platform)
## SRECon 믹스 재생목록
### 동영상
\* [Adobe - The Good, the Bad and the Ugly: The 3 Learnings of an SRE](https://www.usenix.org/conference/srecon20americas/presentation/charagondla)
\* [Amdocs - SREs at Telecom and Media Industry: Bridging between Legacy and Cloud Native Apps](https://www.usenix.org/conference/srecon20americas/presentation/yitzhaki)
\* [Amazon - Confessions of a Systems Engineer: Learning from My 20+ Years of Failure](https://www.usenix.org/conference/srecon20americas/presentation/argent)
\* [Alaska Airlines - Capacity Prediction in External Services](https://www.usenix.org/conference/srecon19americas/presentation/kraus)
\* [BuzzFeed - Optimizing for Learning](https://www.usenix.org/conference/srecon19americas/presentation/mcdonald)
\* [BT - Challenges of Starting an SRE Team from Scratch in an Enterprise](https://www.usenix.org/conference/srecon20americas/presentation/narvas)
\* [Cloudflare - Support Operations Engineering: Scaling Developer Products to the Millions](https://www.usenix.org/conference/srecon19emea/presentation/ali)
\* [Cloudlock - My Life as a Solo SRE](https://www.usenix.org/conference/srecon19emea/presentation/murphy)
\* [Hudson River Trading - Fixing On-Call When Nobody Thinks It's (Too) Broken](https://www.usenix.org/conference/srecon19americas/presentation/lykke)
\* [IBM - Why Automating Everything Adds to Your Toil](https://www.usenix.org/conference/srecon19emea/presentation/thorne)
\* [Genesys - The Smallest Possible SRE Team](https://www.usenix.org/conference/srecon20americas/presentation/thomas)
\* [Grafana Labs - SRE in the Third Age](https://www.usenix.org/conference/srecon19emea/presentation/rabenstein)
\* [Kenna Security - Building a Scalable Monitoring System](https://www.usenix.org/conference/srecon19emea/presentation/struve)
\* [Lightstep - Building Service Ownership Using Documentation, Telemetry, and a Chance to Make Things Better](https://www.usenix.org/conference/srecon20americas/presentation/spoonhower)
\* [MessageBird - Autopsy of a MySQL Automation Disaster](https://www.usenix.org/conference/srecon19emea/presentation/gagne)
\* [Netlify - Perks and Pitfalls of Building a Remote First Team](https://www.usenix.org/conference/srecon19emea/presentation/neal)
\* [ReactiveOps - Zero to SRE](https://www.usenix.org/conference/srecon19americas/presentation/schlesinger)
\* [Salesforce - Incident Response in Unfamiliar Sociotechnical Systems: One Incident Commander's Challenges Supporting Inter-organizational Anomaly Response in the Age of COVID-19](https://www.usenix.org/conference/srecon20americas/presentation/collins)
\* [Sprax - From Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations](https://www.usenix.org/conference/srecon19emea/presentation/huxtable)
\* [The New York Times - SRE by Influence, Not Authority: How the New York Times Prepares for Large-Scale Events](https://www.usenix.org/conference/srecon19emea/presentation/wan)
\* [Twitter - Hiring Great SREs](https://www.usenix.org/conference/srecon19emea/presentation/rutkin)
\* [United States Digital Service - Lessons Learned in Black Box Monitoring 25,000 Endpoints and Proving the SRE Team's Value](https://www.usenix.org/conference/srecon19americas/presentation/wieczorek)
\* [Unity Technologies - Being Reasonable about SRE](https://www.usenix.org/conference/srecon19emea/presentation/urbanec)
\* [Vanguard - Cloudy with a Chance of Chaos](https://www.usenix.org/conference/srecon20americas/presentation/yakomin)
\* [WeWork - Learning from Learnings: Anatomy of Three Incidents](https://www.usenix.org/conference/srecon19americas/presentation/shoup)
\* [Zendesk - Latency and Availability Error Budgets Done Right at Scale](https://www.usenix.org/conference/srecon20americas/presentation/moyer)
---
## 리소스
### 📚 도서
\* 📔 [Site Reliability Engineering](https://amzn

.to/4jNrENP) | [Google이 호스팅하는 무료 온라인 버전 읽기](https://sre.google/sre-book/table-of-contents/)
\* 📔 [Google의 The Site Reliability Workbook](https://amzn.to/3CyRCEa) | [Google이 호스팅하는 무료 온라인 버전 읽기](https://sre.google/workbook/table-of-contents/)
\* 📔 [Seeking SRE](https://amzn.to/3WSmSVu)
\* 📔 [Building Secure & Reliable Systems](https://amzn.to/4gty0yV)
\* 📔 [Enterprise Roadmap to SRE](https://learning.oreilly.com/library/view/enterprise-roadmap-to/9781098117740/)
\* 📔 [Training Site Reliability Engineers](https://www.oreilly.com/library/view/training-site-reliability/9781492076018/) | [Google이 호스팅하는 무료 온라인 버전 읽기](https://github.com/google/googlesre/blob/main/publications/Training\_Site\_Reliability\_Engineers.pdf)
\* 📔 [97 Things Every SRE Should Know](https://amzn.to/4hPCktG)
\* 📔 [SLO Adoption and Usage in Site Reliability Engineering](https://www.oreilly.com/library/view/slo-adoption-and/9781492075370/)
\* 📔 [Practical Site Reliability Engineering](https://amzn.to/4aOFQSL)
\* 📔 [Implementing Service Level Objectives](https://amzn.to/40Ow2nc)
\* 📔 [Database Reliability Engineering](https://amzn.to/4hPCYr6)
\* 📔 [What Is SRE?](https://www.oreilly.com/library/view/what-is-sre/9781492054429/)
\* 📔 [Database Reliability Engineering: What, Why, and How?](https://www.oreilly.com/library/view/database-reliability-engineering/9781492030942/)
\* 📔 [Observability Engineering](https://amzn.to/4hSrVNP)
\* 📔 [Incident Metrics in SRE](https://www.oreilly.com/library/view/incident-metrics-in/9781098103163/) | [Google이 호스팅하는 무료 온라인 버전 읽기](https://sre.google/resources/practices-and-processes/incident-metrics-in-sre/)
\* 📔 [Engineering Reliable Mobile Applications](https://www.oreilly.com/library/view/engineering-reliable-mobile/9781492057444/)
\* 📔 [Monitoring the SRE Golden Signals](https://www.slideshare.net/OpsStack/how-to-monitoring-the-sre-golden-signals-ebook)
\* 📔 [Site Reliability Engineering: Philosophies, habits, and tools for SRE success](https://newrelic.com/resources/ebooks/site-reliability-engineering) | [포터블 버전](https://newrelic.com/sites/default/files/2021-08/site-reliability-engineering-handbook.pdf)
\* 📔 [97 Things Every Cloud Engineer Should Know](https://www.redhat.com/rhdc/managed-files/cl-97-things-cloud-engineers-know-e-book-oreilly-f28602-202105-en.pdf)
\* 📔 [Real-World SRE](https://amzn.to/4hQNhuK)
\* [Hands-on Site Reliability Engineering](https://amzn.to/3EwwNK8)
\* 📔 [High Performance SRE: Automation, error budgeting, RPAs, SLOs, and SLAs with site reliability engineering](https://amzn.to/4hMN4ZE)
\* 📔 [Chaos Engineering: System Resiliency in Practice](https://amzn.to/40OSVa8)
\* 📔 [Chaos Engineering: Site reliability through controlled disruption](https://amzn.to/40PbMSm)
\* 📔 [Security Chaos Engineering: Sustaining Resilience in Software and Systems](https://amzn.to/4hQeTjS)
\* 📔 [Learning Chaos Engineering: Discovering and Overcoming System Weaknesses Through Experimentation](https://amzn.to/4hRDkgz)
\* 📔 [Chaos Engineering Observability](https://www.oreilly.com/library/view/chaos-engineering-observability/9781492051046/)
\* 📔 [Becoming a Rockstar SRE](https://amzn.to/42MOqPZ)
\* 📔 [Becoming SRE, First Steps Toward Reliability for You and Your Organization](https://amzn.to/4jMBU95)
\* 📔 [Establishing SRE Foundations: A Step-by-Step Guide to Introducing Site Reliability Engineering in Software Delivery Organizations](https://amzn.to/4i87f4D)
\* 📔 [The Art of Site Reliability Engineering (SRE) with Azure: Building and Deploying Applications That Endure](https://amzn.to/4hP2VXx)
### 이벤트
\* [SRECon 지난 이벤트](https://www.usenix.org/srecon#past)
\* [ChaosConf](https://www.chaosconf.io/)
\* [SLOConf](https://www.sloconf.com/)
\* [SLOConf 2021 재생목록](https://www.youtube.com/watch?v=-lHPDx90Ppg&list=PLLNq9CBV7AFwyRzICyCRKdcsAPAlG5bPu)
\* [cdCon](https://events.linuxfoundation.org/cdcon/)
\* [cdCon 2021 재생목록](https://www.youtube.com/watch

?v=MQU4fKhau1w&list=PL2KXbZ9-EY9TWsV-Jz8ARSt1ko0Yd36ah)
\* [cdCon 2020 재생목록](https://www.youtube.com/watch?v=qLMrcEj-R9Y&list=PL2KXbZ9-EY9RbYURc1CDrOJpbrPMtc0P7)
\* [Conf42](https://www.conf42.com/sre2022)
\* [Conf42 2022 프리미어](https://www.youtube.com/watch?v=FclEiSDfX14&ab\_channel=Conf42)
### 기타 리소스
#### 어썸 리스트 (Awesome Lists)
\* [Awesome SRE](https://github.com/dastergon/awesome-sre)
\* [Awesome Site Reliability Engineering Tools](https://github.com/SquadcastHub/awesome-sre-tools)
\* [Awesome Chaos Engineering](https://github.com/dastergon/awesome-chaos-engineering)
\* [Awesome Monitoring](https://github.com/crazy-canux/awesome-monitoring)
\* [Awesome Observability](https://github.com/adriannovegil/awesome-observability)
\* [Awesome MLOps](https://github.com/visenger/awesome-mlops)
\* [ML-Ops.org](https://ml-ops.org/)
#### 다양한 조직의 SRE 리소스
\* [Google SRE 페이지](https://sre.google/)
\* [Google SRE 클래스룸](https://sre.google/classroom/)
\* [Google Cloud SRE 페이지](https://cloud.google.com/sre)
\* [Microsoft SRE 페이지](https://docs.microsoft.com/en-us/azure/site-reliability-engineering/)
\* [LinkedIn의 School of SRE](https://linkedin.github.io/school-of-sre/)
\* [Stripe Increment 매거진 16호 - 신뢰성(Reliability)](https://increment.com/reliability/)
\* [AWS Observability Recipes](https://aws-observability.github.io/aws-o11y-recipes/)
\* [Awesome Sysadmin](https://github.com/awesome-foss/awesome-sysadmin)
#### 장애 및 포스트모템 (Incidents & postmortems)
\* [The Verica 오픈 장애 데이터베이스](https://www.thevoid.community/)
\* [포스트모템 템플릿](https://github.com/dastergon/postmortem-templates)
\* [장애 검토 및 포스트모템 모범 사례](https://blog.pragmaticengineer.com/postmortem-best-practices/)
#### 뉴스레터
\* [SRE Weekly 뉴스레터](https://sreweekly.com/)
\* [Chaos Engineering 뉴스레터](https://chaosengineering.news/)
\* [DevOps Weekly 뉴스레터](http://devopsweekly.com)
## 크레딧 (Credits)
\* [Abhijeet Vaikar](https://github.com/abhivaikar)의 [Howtheytest](https://github.com/abhivaikar/howtheytest)에서 영감을 받았습니다.
\* 조직 목록은 저의 다른 저장소인 [awesome-engineering](https://github.com/upgundecha/awesome-engineering)을 참고했습니다.
\* 배너 이미지 [vectorjuice가 제작한 카툰 벡터 - www.freepik.com](https://www.freepik.com/vectors/cartoon)
## 기타 How They... 저장소
\* [Howtheytest](https://github.com/abhivaikar/howtheytest)
\* [Howtheydevops](https://github.com/bregman-arie/howtheydevops)
\* [Howtheyaws](https://github.com/upgundecha/howtheyaws)
\* [Applied AI](https://github.com/upgundecha/applied-ai)
## 기여자 (Contributors)
[![](https://contributors-img.web.app/image?repo=upgundecha/howtheysre)](https://github.com/upgundecha/howtheysre/graphs/contributors)
## 기여하기 (Contribute)
기여는 언제나 환영합니다! 먼저 [기여 가이드라인](contributing.md)을 읽어주세요.
## 시간에 따른 Stargazers 현황
[![Stargazers over time](https://starchart.cc/upgundecha/howtheysre.svg?background=%23FFFFFF&axis=%23333333&line=%23139a15)](https://starchart.cc/upgundecha/howtheysre)
## 라이선스 (License)
[![CC0](https://mirrors.creativecommons.org/presskit/buttons/88x31/svg/cc-zero.svg)](https://creativecommons.org/publicdomain/zero/1.0)
법이 허용하는 최대한의 범위 내에서, Unmesh Gundecha는 이 저작물에 대한 모든 저작권 및 
인접 권리를 포기했습니다.
---
이 내용을 어디선가 사용하게 된다면, X(구 트위터)의 [@upgundecha](https://www.x.com/upgundecha)를 크레딧으로 남겨주세요. 또한 제 작업이 마음에 드셨다면 GitHub에 있는 저의 다른 프로젝트들도 확인해 보세요.

howtheysre

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

howtheysre

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README