https://www.devkuma.com/en/tags/sre/ https://www.devkuma.com/en/tags/sre/logo/180x180.jpg https://www.devkuma.com/en/tags/sre/ Recent content in SRE on devkuma Hugo -- gohugo.io en kc@example.com (kc kim) kc@example.com (kc kim) The devkuma https://www.devkuma.com/en/docs/sre/ Sun, 24 Aug 2025 13:07:00 +0900 kc@example.com (kc kim) https://www.devkuma.com/en/docs/sre/ <h2 id="what-is-sre">What is SRE?</h2> <p>SRE (Site Reliability Engineering) is a software engineering approach to IT operations. SRE uses software as a tool to <strong>manage</strong> systems, <strong>solve</strong> problems, and <strong>automate</strong> operational tasks.</p> <p>SRE is useful for <strong>creating</strong> scalable and highly reliable software systems. Because systems can be <strong>managed</strong> at scale through code, SRE provides greater <strong>scalability</strong> and <strong>sustainability</strong> for system administrators who manage thousands to hundreds of thousands of machines.</p> <p>The concept was created by Gen Treynor Sloss of Google&rsquo;s engineering team.</p> <h2 id="benefits-of-using-sre">Benefits of using SRE</h2> <p>SRE helps release new features on time and allows users to use those features <strong>reliably</strong>.</p> <h3 id="role-of-an-sre-engineer">Role of an SRE engineer</h3> <p>This is a unique role that requires a background such as a software developer with additional operations experience, or a system administrator or IT operator with software development skills.</p> <p>An SRE team is responsible for service availability, latency, change management, emergency response, and capacity management in production, as well as how code is deployed, configured, and monitored.</p> <p>Using service-level agreements (SLAs), service-level indicators (SLIs), and service-level objectives (SLOs), the team can decide what new features to release and when to define reliability requirements for the system.</p> <p>SRE does <strong>not expect 100% reliability</strong> and prepares plans for failures.</p> <h2 id="difference-from-devops">Difference from DevOps</h2> <p>DevOps is an <strong>approach</strong> to company culture, automation, and platform design for improving business value and responsiveness through fast delivery of high-quality services.</p> <p>SRE can be considered an <strong>implementation</strong> of DevOps.</p> <table> <thead> <tr> <th></th> <th>SRE</th> <th>DevOps</th> </tr> </thead> <tbody> <tr> <td>Main focus</td> <td>Scalability, operational metrics, automation</td> <td>Integration of development and deployment processes</td> </tr> <tr> <td>Responsible team</td> <td>Development teams interested in operations</td> <td>Operations teams interested in development</td> </tr> <tr> <td>Metrics</td> <td>Maximum/minimum service-level objectives (SLOs)</td> <td>Mainly system telemetry</td> </tr> <tr> <td>Typical adopters</td> <td>IT service companies in cloud-native environments</td> <td>Companies moving from on-premises to cloud</td> </tr> </tbody> </table> SRE