Site Reliability Engineering
Site reliability engineering is a set of principles and practices that incorporates aspects of software engineering and applies them to infrastructure and operations problems. The main goals are to create scalable and highly reliable software systems.
- What is SRE stands for?
Site reliability engineering (SRE) is a software engineering approach to IT operations. SRE teams use software as a tool to manage systems, solve problems, and automate operations tasks.
2. What is SRE vs DevOps?
SRE vs DevOps — how are they different? Simply speaking, DevOps is for writing and deploying code. SRE, on the other hand, is more comprehensive, with the team taking a wider ‘end-user’s’ perspective while working on the system. A DevOps team works on a product or app using an agile approach.
3. What are the five pillars of SRE?
However, we can define ways to give acceptable and reliable end user experience.
- Service Level Objectives and Indicators (SLO and SLI) Let’s understand Service Indicators first.
- Risk acceptance and mitigation plan.
- Automation, Automation and Automation.
- Proactive Monitoring.
- Release and deployment.
4. Is SRE above DevOps?
The concept of Site Reliability Engineer (SRE) has been around since 2003, making it even older than DevOps.
5. What problem does SRE solve?
A major goal of SRE is to reduce duplication or redundancy of effort as much as possible. SRE teams focus on automating manual tasks, such as provisioning access and infrastructure, setting up accounts, and building self-service tools.