Site reliability engineering

As explained in Effective Platform Engineering

Site reliability engineering is a software engineering discipline that applies engineering practices to the reliability, operation, and lifecycle management of systems.

Site reliability engineering (SRE) applies software engineering practices to operations and the complete service lifecycle, balancing innovation with dependable delivery. section 10.4.1 section 1.4

SRE organizes reliability work around three operational controls:

• Service level objectives (SLOs) define target performance and availability based on user expectations. section 10.4.1 section 10.4.2
• Service level indicators (SLIs) measure compliance through metrics such as latency, throughput, and error rates. section 10.4.1
• Error budgets define acceptable risk and help teams trade change velocity against system stability. section 10.4.1 section 10.4.3

SRE works as a temporary, embedded improvement capability rather than an operational silo. Engineers join mature product or platform teams, improve their lifecycle code and workflows, and transfer those lessons across teams. section 1.4.3

Reliability for payment processing

A team can define SLOs and SLIs for payment processing, monitor them with Prometheus and Grafana, and automate remediation for common failures. Automated recovery, rollbacks, and self-healing reduce manual intervention, downtime, and recovery time. section 10.4.2 section 10.4.4

Figure 1.6 There is a direct connection between each of these enablers and the resulting quality and effect of a platform.

Use the platform-enablement diagram to relate SRE and other enabling practices to platform quality and organizational effect. section 1.4

How Effective Platform Engineering covers it

How deep it goes

Explains SLOs, SLIs, error budgets, monitoring, remediation, and embedded team practice, stopping short of detailed implementation procedures.

Examples

Uses payment processing, Prometheus, Grafana, automated remediation, rollbacks, and self-healing mechanisms as concrete examples.

What it assumes

Assumes mature development or platform teams able to absorb embedded reliability practices into everyday workflows.

What you can do after

Apply it via SLOs, SLIs, error budgets, proactive monitoring, automated remediation, and data-driven reliability prioritization.

How it connects

Connects reliability engineering with platform engineering, DevOps, monitoring, automated remediation, SLOs, SLIs, and error budgets.

liveBookmanning.com

Read Effective Platform Engineering on liveBook Get the book at manning.com

Related concepts

• DevOpskind of · DevOps is a set of organizational, cultural, and technical practices that integrates software development and IT operations through collaboration, automation, and feedback.
• error budgetuses · An error budget is the allowable amount of error or unreliability under a defined objective or constraint.
• platform engineeringuses · Platform engineering is the discipline of designing and operating internal platforms that provide software teams with reusable, self-service capabilities and delivery workflows.
• data-driven approachproduces · A data-driven approach bases decisions, conclusions, or system behavior substantially on collected or observed data rather than primarily on intuition or assumptions.
• service-level objectivehas part · A service-level objective is a target value or range for a measurable service-level indicator over a specified period.

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.