SRE Engagement Model

SRE team uses some technical and procedural approaches to analyze and improve the reliability service. These techniques include early engagement, continuous improvement, Production Readiness Reviews (PRRs), and many more.

The goal of SRE is to maximize the engineering Velocity of developer teams and keep products reliable. Sometimes it measures the limit of how much the SRE team can accomplish. If the domain is complicated or broad, the SRE model becomes less effective. In large cases, the SRE team needs to decide where to get the best result. Here the SRE team and product development team can work together. 

SRE Service Lifecycle

The service life cycle goes through many phases. SRE team involves in every phase. Even the SRE team may begin their work at any stage. 

Level of SRE Engagement during the Service Lifecycle

Level 1: Architecture and Design

SRE influences architecture and design in many ways, like:

• Creates best practices among the team
• Finds the Dos and Don’ts to help developers choosing the best building block
• Provides engagement consulting as early as possible Thus it helps to discuss architecture and design in detail
• Join the developer team to participate in development work.
• SRE engagement helps to reduce the cost of redesign. 

Level 2: Active Development

At this level, the product starts to take shape. Here SRE starts productionizing the service. It includes planning, getting extra resources, handling overload, implementing load balance, monitoring, alerting, performance tuning, and many more.

Level 3: Limited Availability

Here SRE helps to measure and evaluate reliability. The product team can easily withdraw a product that cannot meet the expectation. SRE team builds the capacity model to scale the system, setting resources for upcoming levels and automating service resizing. 

Level 4: General Availability

The level where the service passes the Production Readiness Review and accepts all users. SRE team performs most of the operational work, and the developer team takes the responsibility of maturing the service. 

Level 5: Deprecation

No system is available for a lifetime. A new and better system will take the place of the available network. SRE team also focuses on transforming from an existing system to the new one. When SRE effort in the current order reduces, it effectively supports both the headcount and stuffing system and adjusts them accordingly.

Level 6: Abandoned

When a service gets abandoned, the developer team resumes all operational support. SRE hands over service management to the remaining internal users. 

Level 7: Unsupported

Now the last level and no more users are available. So all the services shut down. SRE deletes the references, including production configurations and documentation. 

In this model, the SRE team engages with the developer team. They build the product and the service team to determine how it should evolve. Engagement of SRE helps to reduce costs and save time. It also makes the final products and services effective and efficient. Visit Runnel.ai