Site reliability engineering - Lightning Talk
•Download as PPTX, PDF•
1 like•256 views
A brief introduction into Site Reliability Engineering concepts of service level objects, service level indicators, and service level agreements.
Report
Share
Report
Share
Recommended
Site reliability engineering
This document discusses site reliability engineering (SRE) for growing organizations. SRE focuses on production automation, resiliency and scalability, similar to devops but with more emphasis on keeping systems running. As companies grow, expectations often outpace capacity and complexity increases, requiring more automation rather than personnel to maintain high uptime levels. A dedicated SRE team can improve reaction times, learn from incidents, raise awareness of system behaviors, and focus on forward-looking improvements rather than just keeping existing systems running. Key SRE practices include automated monitoring, log indexing, health checks, establishing service level objectives and agreements, and implementing self-healing systems and runbooks.
Site (Service) Reliability Engineering
An overview of Google's Site Reliability Engineering with a view toward possible incorporation in the IEEE P2675 DevOps security standard. (Creative Commons with credit.)
Implementing SRE practices: SLI/SLO deep dive - David Blank-Edelman - DevOpsD...
This document discusses best practices for site reliability engineering (SRE). It recommends hiring only coders, establishing service level agreements (SLAs) and measuring performance against them. It also suggests using error budgets, maintaining a common staffing pool for SRE and development teams, ensuring on-call teams have at least 8 people, and conducting post-mortems after every incident. Key reliability metrics like availability, latency, throughput and quality are identified. Objectives, service level objectives (SLOs) and responses if the error budget is exceeded or exhausted are outlined.
Site Reliability Engineering (SRE) - Tech Talk by Keet Sugathadasa
When it comes to Site Reliability Engineering, short for SRE, the resources available online are only limited to the books published by Google themselves. They do share some useful case studies that will help us understand what SRE is, and how to understand the concepts given in it, but they do not clearly explain how to build your own SRE team for your organization. The concept of SRE was cooked fresh within the walls of Google and later released to the general public as a practice for anyone to follow.
In this presentation I would like to give a brief introduction to SRE and why it is important to any Software Engineering organization. This is based on my experiences and learnings from leading a Site Reliability Engineering team for leading organizations in the US and Norway.
This presentation was conducted by me as a Tech Talk as an Associate Technical Lead at Creative Software Sri Lanka.
SRE in Startup
SRE (Site Reliability Engineering) is responsible for availability, latency, performance, efficiency, change management, monitoring, emergency response, and capacity planning of services. An SRE team uses an "error budget" approach where new features can be launched if the service is within its agreed SLA, but launches are frozen if the SLA is not being met until enough of the error budget is earned back. SRE teams hire only coders who can speak the same language as developers and rotate developers into operations work. The goal of SRE is to minimize impact and prevent recurrence of outages through practices like post-mortem analysis and constant improvement of processes.
SRE (service reliability engineer) on big DevOps platform running on the clou...
SRE (service reliability engineer). The talk is to explain the SRE philosophy and the principles of production engineering and operations in clouds.
(Language – English)
Pavlo is ADOP (Accenture DevOps Platform) Service Reliability Team Lead, SRE practitioner. Has more then 18 years of IT experience in Ops and Dev.
Sre summary
SRE stands for Site Reliability Engineering. It originated at Google over a decade ago as a way to ensure their products and services were highly reliable. SRE implements DevOps principles through components like reliability, service level agreements (SLAs), service level objectives (SLOs), service level indicators (SLIs), and error budgets. Reliability is measured through SLOs and SLIs to quantify user experience. Error budgets allow teams to balance new features against reliability by quantifying how much downtime is acceptable. SRE aims to reduce "toil", or unnecessary repetitive manual work, through automation.
Getting started with Site Reliability Engineering (SRE)
"Getting started with Site Reliability Engineering (SRE): A guide to improving systems reliability at production"
This is an intro guide to share some of the common concepts of SRE to a non-technical audience. We will look at both technical and organizational changes that should be adopted to increase operational efficiency, ultimately benefiting for global optimizations - such as minimize downtime, improve systems architecture & infrastructure:
- improving incident response
- Defining error budgets
- Better monitoring of systems
- Getting the best out of systems alerting
- Eliminating manual, repetitive actions (toils) by automation
- Designing better on-call shifts/rotations
How to design the role of the Site Reliability Engineer (who effectively works between application development teams and operations support teams)
Recommended
Site reliability engineering
This document discusses site reliability engineering (SRE) for growing organizations. SRE focuses on production automation, resiliency and scalability, similar to devops but with more emphasis on keeping systems running. As companies grow, expectations often outpace capacity and complexity increases, requiring more automation rather than personnel to maintain high uptime levels. A dedicated SRE team can improve reaction times, learn from incidents, raise awareness of system behaviors, and focus on forward-looking improvements rather than just keeping existing systems running. Key SRE practices include automated monitoring, log indexing, health checks, establishing service level objectives and agreements, and implementing self-healing systems and runbooks.
Site (Service) Reliability Engineering
An overview of Google's Site Reliability Engineering with a view toward possible incorporation in the IEEE P2675 DevOps security standard. (Creative Commons with credit.)
Implementing SRE practices: SLI/SLO deep dive - David Blank-Edelman - DevOpsD...
This document discusses best practices for site reliability engineering (SRE). It recommends hiring only coders, establishing service level agreements (SLAs) and measuring performance against them. It also suggests using error budgets, maintaining a common staffing pool for SRE and development teams, ensuring on-call teams have at least 8 people, and conducting post-mortems after every incident. Key reliability metrics like availability, latency, throughput and quality are identified. Objectives, service level objectives (SLOs) and responses if the error budget is exceeded or exhausted are outlined.
Site Reliability Engineering (SRE) - Tech Talk by Keet Sugathadasa
When it comes to Site Reliability Engineering, short for SRE, the resources available online are only limited to the books published by Google themselves. They do share some useful case studies that will help us understand what SRE is, and how to understand the concepts given in it, but they do not clearly explain how to build your own SRE team for your organization. The concept of SRE was cooked fresh within the walls of Google and later released to the general public as a practice for anyone to follow.
In this presentation I would like to give a brief introduction to SRE and why it is important to any Software Engineering organization. This is based on my experiences and learnings from leading a Site Reliability Engineering team for leading organizations in the US and Norway.
This presentation was conducted by me as a Tech Talk as an Associate Technical Lead at Creative Software Sri Lanka.
SRE in Startup
SRE (Site Reliability Engineering) is responsible for availability, latency, performance, efficiency, change management, monitoring, emergency response, and capacity planning of services. An SRE team uses an "error budget" approach where new features can be launched if the service is within its agreed SLA, but launches are frozen if the SLA is not being met until enough of the error budget is earned back. SRE teams hire only coders who can speak the same language as developers and rotate developers into operations work. The goal of SRE is to minimize impact and prevent recurrence of outages through practices like post-mortem analysis and constant improvement of processes.
SRE (service reliability engineer) on big DevOps platform running on the clou...
SRE (service reliability engineer). The talk is to explain the SRE philosophy and the principles of production engineering and operations in clouds.
(Language – English)
Pavlo is ADOP (Accenture DevOps Platform) Service Reliability Team Lead, SRE practitioner. Has more then 18 years of IT experience in Ops and Dev.
Sre summary
SRE stands for Site Reliability Engineering. It originated at Google over a decade ago as a way to ensure their products and services were highly reliable. SRE implements DevOps principles through components like reliability, service level agreements (SLAs), service level objectives (SLOs), service level indicators (SLIs), and error budgets. Reliability is measured through SLOs and SLIs to quantify user experience. Error budgets allow teams to balance new features against reliability by quantifying how much downtime is acceptable. SRE aims to reduce "toil", or unnecessary repetitive manual work, through automation.
Getting started with Site Reliability Engineering (SRE)
"Getting started with Site Reliability Engineering (SRE): A guide to improving systems reliability at production"
This is an intro guide to share some of the common concepts of SRE to a non-technical audience. We will look at both technical and organizational changes that should be adopted to increase operational efficiency, ultimately benefiting for global optimizations - such as minimize downtime, improve systems architecture & infrastructure:
- improving incident response
- Defining error budgets
- Better monitoring of systems
- Getting the best out of systems alerting
- Eliminating manual, repetitive actions (toils) by automation
- Designing better on-call shifts/rotations
How to design the role of the Site Reliability Engineer (who effectively works between application development teams and operations support teams)
Overview of Site Reliability Engineering (SRE) & best practices
In any software organization, stability & innovation are always at loggerheads - the faster you move, the more things will break. This talk defines what SRE org looks like at high-tech organizations (Google, Uber).
SRE-iously! Reliability!
The document discusses Site Reliability Engineering (SRE) practices at New Relic. It summarizes that New Relic has transitioned from a monolithic architecture run by siloed teams to over 200 microservices run by many engineering teams with embedded SREs. SREs aim to continuously improve reliability by reducing toil, encouraging best practices, automating operations, and supporting engineering teams. SREs focus on stability, reliability engineering, and reducing operations toil. The document provides a template for other companies to establish SRE roles, focus areas, and details in the SRE book.
Site Reliability Engineering: An Enterprise Adoption Story (an ITSM Academy W...
Presenter: Perry Statham
SRE Squad Leader with IBM Cloud DevOps Services
In this presentation, the IBM DevOps Services SRE team will give a brief introduction to Site Reliability Engineering, then show how they adopted its principals in their existing enterprise organization.
SRE 101
This document provides an introduction to Site Reliability Engineering (SRE). It lists the credentials and background of Diego Pacheco, including his roles as a cat's father, principal software architect, agile coach, and expert in SOA/microservices, DevOps, and observability. The document then defines SRE as "what happens when you ask a software engineer to design an operations function" and outlines some key aspects of SRE culture, including MTTD, MTTR, error budgets, jitter retries, exponential back-off, the "You build it you run it" mindset, and production readiness.
How Small Team Get Ready for SRE (public version)
This document discusses how small teams can get ready for Site Reliability Engineering (SRE). It describes the challenges faced by a small engineering team at a company with around 100 employees and 10 engineers. To address issues with productivity, reliability, and deployment speed, the team implemented several initiatives including adopting SCRUM, adding automated testing, simplifying deployments, and creating easy-to-use development environments. While these changes helped, the team knows there is still work needed in areas like data center operations and establishing formal SLAs and incident management processes as the company and services grow. The presentation concludes by discussing why SRE is preferable to just DevOps and provides resources for further learning.
DevOps Torino Meetup - SRE Concepts
Independently from the DevOps movement but starting from the same problems, Google developed its own strategy defining a new specific role called SRE (Site Reliability Engineer). This introduction tries to explain the history and the concept of this methodology and to compare it with the DevOps manifesto to understand what does it mean to adopt DevOps and what does it mean to be an SRE and what the two things are sharing and where they diverge.
SRE 101 (Site Reliability Engineering)
This document provides an introduction to Site Reliability Engineering (SRE). It discusses DevOps principles and how SRE relates to and implements DevOps. Key aspects of SRE covered include guiding principles like eliminating toil, embracing risk, and measuring services through SLIs, SLOs, and error budgets. Specific SRE practices mentioned are removing toil, defining system criticalities, designing for availability, observability, chaos engineering, restricting production access, and focusing on metrics like MTTR and MTBF.
SRE Demystified - 01 - SLO SLI and SLA
According to Google, SRE is what you get when you treat operations as if it’s a software problem. In this video, I briefly explain the term SRE (Site Reliability Engineering) and introduce key metrics for an SRE team SLI, SLO, and SLA.
Youtube Channel here: https://www.youtube.com/playlist?list=PLm_COkBtXzFq5uxmamT0tqXo-aKftLC1U
A Crash Course in Building Site Reliability
<p>From <a href="https://en.wikipedia.org/wiki/Site_reliability_engineering" target="_blank">Wikipedia</a>: Site reliability engineering (SRE) is a discipline that incorporates aspects of software engineering and applies that to operations whose goals are to create ultra-scalable and highly reliable software systems.<p>
<p>Over the past year Acquia has built their own SRE team to help their products and services scale with the demand of our growing number of customers. We wish to share our experience so that others are enabled to do the same and reap the rewards.</p>
<p>This presentation will discuss how the SRE team came about at Acquia, what achievements we have made so far, and the lessons we have learned along the way. We will then show the steps on how to introduce SRE to your workplace so you can deliver more reliable and scalable services to your customers! We will specifically cover:</p>
<ul>
<li>SRE's basic concepts and history from Google</li>
<li>The management support you will need to get started</li>
<li>Introducing the idea of service level objectives and error budgets</li>
<li>Operational Responsibility Assessments as a tool to measure risk</li>
<li>Creating a Launch Readiness Checklist to standardize and improve product launches</li>
<li>Finding ideal candidates for your SRE team</li></ul>
<p>The intended audience are software engineers, system administrators, and managers that have a desire to improve how they do their work and how their products/services perform.</p>
Service Level Terminology : SLA ,SLO & SLI
1. SRE is the discipline of applying software engineering practices to solve operations problems to build reliable systems.
2. Service level terminology includes Service Level Indicators (SLIs) which are quantitative measures of service aspects like latency or error rates, Service Level Objectives (SLOs) which are goals for specific metrics, and Service Level Agreements (SLAs) which are agreements within an SLA.
3. Choosing the right SLIs, crafting meaningful SLOs, collecting indicator data, and meeting customer expectations through SLAs are important for building reliable services.
SRE-iously! Defining the Principles, Habits, and Practices of Site Reliabilit...
The document discusses the principles, habits, and practices of site reliability engineering (SRE) at New Relic. It describes New Relic's transition from a monolithic architecture with siloed teams to a microservices architecture with 200+ services and embedded SREs on engineering teams. The goals of SREs at New Relic are to continuously improve the reliability of their platform through two main roles: "pure" SREs who build core platforms and embedded SREs who partner with engineering teams. SREs focus on three spheres: stability, reliability, and engineering.
Building an SRE Organization @ Squarespace
The document discusses the growth of Site Reliability Engineering (SRE) at Squarespace from a team of 2 people in New York to a global organization with teams in New York, Portland, and Dublin. It describes how the initial SRE team focused on three pillars: monitoring and alerting, configuration management, and builds and deploys. It then explains how the SRE organization expanded to include additional teams focused on areas like provisioning, release engineering, developer productivity, and observability while also embedding SREs within product teams.
What's an SRE at Criteo - Meetup SRE Paris
This document summarizes the role of a Site Reliability Engineer (SRE) at Criteo. It discusses how Criteo embraced a DevOps philosophy by breaking down barriers between development and operations teams. SREs at Criteo work in small, specialized teams to maintain infrastructure and platforms while also providing support, automation, and on-call responsibilities. Their goal is to enable development teams through ownership of the services they provide and collaboration across organizational boundaries.
The Next Wave of Reliability Engineering
In 2018, Site Reliability Engineering (SRE) will turn 15 years old. Since Google's inception of the term SRE, companies across the world have adopted a new operations mindset along with automation, deployment and monitoring principals. Most of what SRE does now is well established throughout the industry, so what is the next-wave of reliability principals and automation frameworks?
This session will dive into what the future holds for reliability engineering as a field and what will be the next areas of investment and improvement for reliability teams.
SRE Demystified - 05 - Toil Elimination
According to Google, SRE is what you get when you treat operations as if it’s a software problem. In this video, I briefly explain what is and isn't toil, how to identify, measure and eliminate them.
Youtube channel here: https://youtu.be/EgpCw15fIK8
DevOps vs. Site Reliability Engineering (SRE) in Age of Kubernetes
There is a transformation brewing for DevOps in age of Kubernetes. The tools of the trade, configuration management solutions, have been superseded in agility and preference by development teams who want the declarative choreography of containerized applications. The new preference for mixing developer and operations is the site reliability engineering (SRE) model championed by Google. In this new structure, the need to automate doesn’t stop at the containerized application and DevOps professionals should seek to automate the Kubernetes service itself.
In this webinar, Chris Gaun, Product Marketing Manager at Mesosphere, will cover:
The transformation of DevOps to SRE
How Kubernetes and DC/OS were catalyst for this change
How DevOps professionals can get started with Kubernetes
WHO SHOULD ATTEND
Tech Professionals
Developer Managers
IT Managers
Note the material is technical and is not intended as sales and marketing training
SRE From Scratch
This document provides an overview of site reliability engineering (SRE). It discusses that SREs work to keep sites up, know the production environment, and help build infrastructure for monitoring, deployment, and automation. Hiring SREs can help improve uptime and utilize their experience from similar systems at scale. SREs should be involved in discussions affecting the production environment and help make software more reliable and fault-tolerant.
Setting SLOs and SLIs in the Real World
Clearly defined and well-measured Service Level Objectives (SLOs) and Service Level Indicators (SLIs) are a key pillar of any reliability program. SLOs allow organizations and teams to make smart, data-driven decisions about risk and the right balance of investment between reliability and product velocity.
Site Reliability Engineer (SRE), We Keep The Lights On 24/7
There are many phases in the software development cycle, from requirements to development and testing, but at the tail of the process, is an often overlooked aspect: deployment and delivery. With the paradigm shift of delivering on-site software to offering software-as-a-service, Site Reliability Engineering is beginning to take a greater role in product delivery.
This session aims to give a glimpse of the work that goes into site reliability engineering (SRE) and effort that goes into keeping a service going 24/7.
What is Site Reliability Engineering (SRE)
Site reliability engineering (SRE) is a set of principles that applies software engineering practices to infrastructure and operations. SRE teams use automation and software development skills to manage systems and solve problems in order to create highly reliable and scalable software systems. SRE teams are responsible for availability, performance, monitoring, change management, emergency response, and capacity planning within an engineering organization. SRE focuses on automation, system design, and improvements to system resilience.
TaaS Webinar
Amazon pioneered cloud services in 2006 thereby providing organizations the capability to flexibly scale their infrastructure with high reliability. Since then other cloud service providers like Microsoft, Google and others have joined the bandwagon with the central idea of enabling its customers to completely outsource the overhead of managing their infrastructure. This has paved the ground for various offerings for infrastructure management commonly known as Infrastructure-as-a-Service (IaaS). These offerings have enabled companies to experiment with new ideas and continue iterations with minimal upfront investment.
The human resource management landscape is ripe for a similar disruption. Companies are realizing that flexible on-demand human resource provisioning can enable it to solve business challenges better, faster and cheaper. Resource services being available on demand is often referred to as Testing-as-a-Service (TaaS). TaaS enables organizations get to right on-demand workforce which can thrive in the continuously evolving digital landscape. This allows companies to be more responsive and focused on user needs.
3 Enterprise Storage Assessment
The document provides information about Mainline's Enterprise Storage Assessment service. The assessment evaluates a client's current storage environment, processes, organization, and governance to identify gaps. It then provides deliverables including an overview of the current environment, operational processes, team responsibilities, governance measures, and outage logs. The assessment also defines a target future environment and provides a prioritized roadmap of recommendations to address identified gaps. Mainline's assessment aims to help clients improve their storage services and reduce outages.
More Related Content
What's hot
Overview of Site Reliability Engineering (SRE) & best practices
In any software organization, stability & innovation are always at loggerheads - the faster you move, the more things will break. This talk defines what SRE org looks like at high-tech organizations (Google, Uber).
SRE-iously! Reliability!
The document discusses Site Reliability Engineering (SRE) practices at New Relic. It summarizes that New Relic has transitioned from a monolithic architecture run by siloed teams to over 200 microservices run by many engineering teams with embedded SREs. SREs aim to continuously improve reliability by reducing toil, encouraging best practices, automating operations, and supporting engineering teams. SREs focus on stability, reliability engineering, and reducing operations toil. The document provides a template for other companies to establish SRE roles, focus areas, and details in the SRE book.
Site Reliability Engineering: An Enterprise Adoption Story (an ITSM Academy W...
Presenter: Perry Statham
SRE Squad Leader with IBM Cloud DevOps Services
In this presentation, the IBM DevOps Services SRE team will give a brief introduction to Site Reliability Engineering, then show how they adopted its principals in their existing enterprise organization.
SRE 101
This document provides an introduction to Site Reliability Engineering (SRE). It lists the credentials and background of Diego Pacheco, including his roles as a cat's father, principal software architect, agile coach, and expert in SOA/microservices, DevOps, and observability. The document then defines SRE as "what happens when you ask a software engineer to design an operations function" and outlines some key aspects of SRE culture, including MTTD, MTTR, error budgets, jitter retries, exponential back-off, the "You build it you run it" mindset, and production readiness.
How Small Team Get Ready for SRE (public version)
This document discusses how small teams can get ready for Site Reliability Engineering (SRE). It describes the challenges faced by a small engineering team at a company with around 100 employees and 10 engineers. To address issues with productivity, reliability, and deployment speed, the team implemented several initiatives including adopting SCRUM, adding automated testing, simplifying deployments, and creating easy-to-use development environments. While these changes helped, the team knows there is still work needed in areas like data center operations and establishing formal SLAs and incident management processes as the company and services grow. The presentation concludes by discussing why SRE is preferable to just DevOps and provides resources for further learning.
DevOps Torino Meetup - SRE Concepts
Independently from the DevOps movement but starting from the same problems, Google developed its own strategy defining a new specific role called SRE (Site Reliability Engineer). This introduction tries to explain the history and the concept of this methodology and to compare it with the DevOps manifesto to understand what does it mean to adopt DevOps and what does it mean to be an SRE and what the two things are sharing and where they diverge.
SRE 101 (Site Reliability Engineering)
This document provides an introduction to Site Reliability Engineering (SRE). It discusses DevOps principles and how SRE relates to and implements DevOps. Key aspects of SRE covered include guiding principles like eliminating toil, embracing risk, and measuring services through SLIs, SLOs, and error budgets. Specific SRE practices mentioned are removing toil, defining system criticalities, designing for availability, observability, chaos engineering, restricting production access, and focusing on metrics like MTTR and MTBF.
SRE Demystified - 01 - SLO SLI and SLA
According to Google, SRE is what you get when you treat operations as if it’s a software problem. In this video, I briefly explain the term SRE (Site Reliability Engineering) and introduce key metrics for an SRE team SLI, SLO, and SLA.
Youtube Channel here: https://www.youtube.com/playlist?list=PLm_COkBtXzFq5uxmamT0tqXo-aKftLC1U
A Crash Course in Building Site Reliability
<p>From <a href="https://en.wikipedia.org/wiki/Site_reliability_engineering" target="_blank">Wikipedia</a>: Site reliability engineering (SRE) is a discipline that incorporates aspects of software engineering and applies that to operations whose goals are to create ultra-scalable and highly reliable software systems.<p>
<p>Over the past year Acquia has built their own SRE team to help their products and services scale with the demand of our growing number of customers. We wish to share our experience so that others are enabled to do the same and reap the rewards.</p>
<p>This presentation will discuss how the SRE team came about at Acquia, what achievements we have made so far, and the lessons we have learned along the way. We will then show the steps on how to introduce SRE to your workplace so you can deliver more reliable and scalable services to your customers! We will specifically cover:</p>
<ul>
<li>SRE's basic concepts and history from Google</li>
<li>The management support you will need to get started</li>
<li>Introducing the idea of service level objectives and error budgets</li>
<li>Operational Responsibility Assessments as a tool to measure risk</li>
<li>Creating a Launch Readiness Checklist to standardize and improve product launches</li>
<li>Finding ideal candidates for your SRE team</li></ul>
<p>The intended audience are software engineers, system administrators, and managers that have a desire to improve how they do their work and how their products/services perform.</p>
Service Level Terminology : SLA ,SLO & SLI
1. SRE is the discipline of applying software engineering practices to solve operations problems to build reliable systems.
2. Service level terminology includes Service Level Indicators (SLIs) which are quantitative measures of service aspects like latency or error rates, Service Level Objectives (SLOs) which are goals for specific metrics, and Service Level Agreements (SLAs) which are agreements within an SLA.
3. Choosing the right SLIs, crafting meaningful SLOs, collecting indicator data, and meeting customer expectations through SLAs are important for building reliable services.
SRE-iously! Defining the Principles, Habits, and Practices of Site Reliabilit...
The document discusses the principles, habits, and practices of site reliability engineering (SRE) at New Relic. It describes New Relic's transition from a monolithic architecture with siloed teams to a microservices architecture with 200+ services and embedded SREs on engineering teams. The goals of SREs at New Relic are to continuously improve the reliability of their platform through two main roles: "pure" SREs who build core platforms and embedded SREs who partner with engineering teams. SREs focus on three spheres: stability, reliability, and engineering.
Building an SRE Organization @ Squarespace
The document discusses the growth of Site Reliability Engineering (SRE) at Squarespace from a team of 2 people in New York to a global organization with teams in New York, Portland, and Dublin. It describes how the initial SRE team focused on three pillars: monitoring and alerting, configuration management, and builds and deploys. It then explains how the SRE organization expanded to include additional teams focused on areas like provisioning, release engineering, developer productivity, and observability while also embedding SREs within product teams.
What's an SRE at Criteo - Meetup SRE Paris
This document summarizes the role of a Site Reliability Engineer (SRE) at Criteo. It discusses how Criteo embraced a DevOps philosophy by breaking down barriers between development and operations teams. SREs at Criteo work in small, specialized teams to maintain infrastructure and platforms while also providing support, automation, and on-call responsibilities. Their goal is to enable development teams through ownership of the services they provide and collaboration across organizational boundaries.
The Next Wave of Reliability Engineering
In 2018, Site Reliability Engineering (SRE) will turn 15 years old. Since Google's inception of the term SRE, companies across the world have adopted a new operations mindset along with automation, deployment and monitoring principals. Most of what SRE does now is well established throughout the industry, so what is the next-wave of reliability principals and automation frameworks?
This session will dive into what the future holds for reliability engineering as a field and what will be the next areas of investment and improvement for reliability teams.
SRE Demystified - 05 - Toil Elimination
According to Google, SRE is what you get when you treat operations as if it’s a software problem. In this video, I briefly explain what is and isn't toil, how to identify, measure and eliminate them.
Youtube channel here: https://youtu.be/EgpCw15fIK8
DevOps vs. Site Reliability Engineering (SRE) in Age of Kubernetes
There is a transformation brewing for DevOps in age of Kubernetes. The tools of the trade, configuration management solutions, have been superseded in agility and preference by development teams who want the declarative choreography of containerized applications. The new preference for mixing developer and operations is the site reliability engineering (SRE) model championed by Google. In this new structure, the need to automate doesn’t stop at the containerized application and DevOps professionals should seek to automate the Kubernetes service itself.
In this webinar, Chris Gaun, Product Marketing Manager at Mesosphere, will cover:
The transformation of DevOps to SRE
How Kubernetes and DC/OS were catalyst for this change
How DevOps professionals can get started with Kubernetes
WHO SHOULD ATTEND
Tech Professionals
Developer Managers
IT Managers
Note the material is technical and is not intended as sales and marketing training
SRE From Scratch
This document provides an overview of site reliability engineering (SRE). It discusses that SREs work to keep sites up, know the production environment, and help build infrastructure for monitoring, deployment, and automation. Hiring SREs can help improve uptime and utilize their experience from similar systems at scale. SREs should be involved in discussions affecting the production environment and help make software more reliable and fault-tolerant.
Setting SLOs and SLIs in the Real World
Clearly defined and well-measured Service Level Objectives (SLOs) and Service Level Indicators (SLIs) are a key pillar of any reliability program. SLOs allow organizations and teams to make smart, data-driven decisions about risk and the right balance of investment between reliability and product velocity.
Site Reliability Engineer (SRE), We Keep The Lights On 24/7
There are many phases in the software development cycle, from requirements to development and testing, but at the tail of the process, is an often overlooked aspect: deployment and delivery. With the paradigm shift of delivering on-site software to offering software-as-a-service, Site Reliability Engineering is beginning to take a greater role in product delivery.
This session aims to give a glimpse of the work that goes into site reliability engineering (SRE) and effort that goes into keeping a service going 24/7.
What is Site Reliability Engineering (SRE)
Site reliability engineering (SRE) is a set of principles that applies software engineering practices to infrastructure and operations. SRE teams use automation and software development skills to manage systems and solve problems in order to create highly reliable and scalable software systems. SRE teams are responsible for availability, performance, monitoring, change management, emergency response, and capacity planning within an engineering organization. SRE focuses on automation, system design, and improvements to system resilience.
What's hot (20)
Overview of Site Reliability Engineering (SRE) & best practices
Overview of Site Reliability Engineering (SRE) & best practices
Site Reliability Engineering: An Enterprise Adoption Story (an ITSM Academy W...
Site Reliability Engineering: An Enterprise Adoption Story (an ITSM Academy W...
SRE-iously! Defining the Principles, Habits, and Practices of Site Reliabilit...
SRE-iously! Defining the Principles, Habits, and Practices of Site Reliabilit...
DevOps vs. Site Reliability Engineering (SRE) in Age of Kubernetes
DevOps vs. Site Reliability Engineering (SRE) in Age of Kubernetes
Site Reliability Engineer (SRE), We Keep The Lights On 24/7
Site Reliability Engineer (SRE), We Keep The Lights On 24/7
Similar to Site reliability engineering - Lightning Talk
TaaS Webinar
Amazon pioneered cloud services in 2006 thereby providing organizations the capability to flexibly scale their infrastructure with high reliability. Since then other cloud service providers like Microsoft, Google and others have joined the bandwagon with the central idea of enabling its customers to completely outsource the overhead of managing their infrastructure. This has paved the ground for various offerings for infrastructure management commonly known as Infrastructure-as-a-Service (IaaS). These offerings have enabled companies to experiment with new ideas and continue iterations with minimal upfront investment.
The human resource management landscape is ripe for a similar disruption. Companies are realizing that flexible on-demand human resource provisioning can enable it to solve business challenges better, faster and cheaper. Resource services being available on demand is often referred to as Testing-as-a-Service (TaaS). TaaS enables organizations get to right on-demand workforce which can thrive in the continuously evolving digital landscape. This allows companies to be more responsive and focused on user needs.
3 Enterprise Storage Assessment
The document provides information about Mainline's Enterprise Storage Assessment service. The assessment evaluates a client's current storage environment, processes, organization, and governance to identify gaps. It then provides deliverables including an overview of the current environment, operational processes, team responsibilities, governance measures, and outage logs. The assessment also defines a target future environment and provides a prioritized roadmap of recommendations to address identified gaps. Mainline's assessment aims to help clients improve their storage services and reduce outages.
Azure governance
1. Azure Governance provides native platform capabilities to ensure compliant use of cloud resources through environment factory, policy-based control, and resource visibility features.
2. Environment factory allows users to deploy and update cloud environments in a repeatable manner using composable artifacts like ARM templates.
3. Policy-based control enables real-time policy evaluation and enforcement as well as periodic and on-demand compliance assessment at scale across management groups.
Design patterns and plan for developing high available azure applications
1. Design Patterns High Availability of Azure Applications
2. Practical Demo on points to take care for High Availability from Infrastructure point of view(the points we discussed in last seminar)
3. Different Patterns for High Availability
3.1 Health Endpoint Monitoring Pattern
3.2 Queue-based Load Leveling Pattern
3.2 Throttling Pattern
3.3 Retry Pattern
3.4 Multiple Datacenter Deployment Guidance
4. Architecture for High Availability of Azure Applications
5. best practices for developing High Available Azure Applications
Dimension of quality in Cloud Database Services
In cloud database services quality is measured in terms
a) High Performance
b) High Availability
c) Elastic Scalability
SFDC ODS Preludesys
On-demand services provide flexibility in scaling resources up or down depending on business needs. They allow companies to access additional resources quickly and easily when needed, and scale back when not. On-demand services are becoming an increasingly popular enterprise model as they offer a lower-cost, pay-as-you-go alternative to traditional staffing models.
Performance Testing Strategy for Cloud-Based System using Open Source Testing...
Performance Testing Strategy for Cloud-Based System using Open Source Testing...MIMOS Berhad/Open University Malaysia/Universiti Teknologi Malaysia
This document outlines a performance testing strategy for a cloud-based system using an open source testing tool. It describes introducing virtual users gradually from 1 to 3000 to test response times. Response times remained under 5 seconds for up to 1500 users but slowed for 3000 users. Testing showed faster response for high-speed internet and unloaded servers. The strategy successfully tested the system's ability to handle increasing loads in the cloud. Future work could include hosting the testing tool in the cloud and expanding performance analysis.2 Storage Readiness Assessment
The document describes Mainline's Service Readiness Assessment, which evaluates a company's storage and backup service delivery capabilities. It involves interviews to collect information on processes, organization, technology, and governance. Mainline then scores the results and provides recommendations to improve service delivery compared to industry averages. The assessment takes about 3 hours and provides a same-day initial score and recommendations within a week. It is part of Mainline's larger storage assessment methodology.
Ncerc rlmca202 adm m4 ssm
Automated acceptance testing is an important part of the deployment pipeline. It tests that the application meets business requirements and provides value to users. Creating maintainable acceptance test suites involves deriving tests from acceptance criteria, layering the tests, and avoiding direct coupling to the GUI. Non-functional requirements like performance and capacity also need to be tested. The deployment process should be automated and standardized across environments using techniques like blue-green deployment and canary releases to allow rolling back changes if needed.
Types of performance testing
Performance testing validates an application's responsiveness, stability, and other quality attributes under various workloads. It involves load testing, stress testing, endurance testing, spike testing, volume testing, availability testing, and scalability testing. The key parameters analyzed are response time, throughput, and memory utilization. Performance testing helps determine an application's speed, scalability, stability, and ability to handle changes in load and traffic over time.
Rational Quality Manager
IBM® Rational® Quality Manager is a collaborative, Web-based, quality management tool for comprehensive test planning and test asset management throughout the software lifecycle. It is built on the Jazz™ platform and is designed to be used by test teams of all sizes. It supports a variety of user roles, such as test manager, test architect, test lead, tester, and lab manager, as well as roles outside of the test organization. This article explains how to set up a new project in Rational Quality Manager and reviews several of the basic things that you can do with it in your projects.Strongback Consulting helps organizations get started automated their test environment and improving the quality of the quality management process.
Hidden Costs of Chasing the Mythical 'Five Nines'
“Five Nines” refers to the five nines in 99.999% available that is often synonymous with highly available. Does every highly available service require five nines? Not by a long shot. Yet the general state of the practice is to chase after this typically unrealistic goal almost blindly in many cases, often leading to unnecessarily high costs in both operational and development resources. Even less aggressive availability goals are often over-specified compared to true business drivers.
This talk will cover:
* The history of “five nines”
Common reasons why many organizations often inadvertently over-specify availability requirements
* The costs of such over-specification
* How service agility is negatively affected
* Examples of highly available systems with reasonable availability requirements
* Techniques on how to avoid over-specification based on Site Reliability Engineering principles
* Ways to spend your Error Budget (once you have one) most effectively
Applying these techniques should result in a more cost-effective service that keeps end users and management happy, and fewer alerts to the on-call DevOps engineer.
Jagadeesh_Resume_5 + Years
Jagadeesh Babu has over 5 years of experience in software testing, including functional testing, agile testing, test planning, and test execution. He has expertise in testing mainframe, web, and mobile applications for clients in banking, insurance, and healthcare. Jagadeesh is proficient with testing tools like ALM, QTP, and Selenium and databases like Oracle, DB2, and SQL. He is certified in ISTQB foundations and agile testing methodologies.
S.R.E - create ultra-scalable and highly reliable systems
Site Reliability Engineering enables agility and stability.
SREs use Software Engineering to automate themselves out of the Job.
My advice, if you want to implement this change in your company is to start with action items, alter your training and hiring, implement error budgets, do blameless postmortems and reduce toil.
https://events.drupal.org/dublin2016/sessions/sre-create-ultra-scalable-and-highly-reliable-systems
typesofperformancetesting-130505055525-phpapp02.pdf
Performance testing validates an application's responsiveness, stability, and other quality attributes under various workloads. It involves load testing, stress testing, endurance testing, spike testing, volume testing, availability testing, and scalability testing to observe key parameters like response time, throughput, and memory utilization. The objectives are to evaluate an application's speed, scalability, and stability as load increases and to identify its breaking point.
Top 10 Business Reasons for ALM
Why should your business focus on Application Lifecycle Management? What benefits will you see to your overall business? How does ALM impact your bottom line? View this slideshare to discover all the answers!
Top Business Benefits of Application Lifecycle Management (ALM)
Why should your business focus on Application Lifecycle Management? What benefits will you see to your overall business? How does ALM impact your bottom line? Come attend this free webinar to discover all the answers!
Welingkar First Year Project- ProjectWeLike
This is my first year Semester-2 project this project contains:-
1- WeTude - 5 Topics covered
2- WeLounge - 3 Topics Coverd
3- NewsWire- 10 Lastest NEWS from the IT industry.
This 3 above platform is integrated with the WeSchool-Distance-MBA course (PGDM-D).
Thank you. Be Happy.
Cloudbyz ppm, integrated enterprise ppm-alm-apm on force.com
Cloudbyz PPM is an integrated enterprise project portfolio management (PPM), application life cycle management (ALM) and application portfolio management (APM) built on Salesforce 1 platform. Cloudbyz PPM is focused on providing agility, real-time visibility and enhanced collaboration and productivity to CIO / IT organization.
Module -4 Resource Management.pdf
Resource management cloud (RMC) provides businesses with tools to optimize their IT resource usage, reduce costs, and improve performance. Some key benefits of RMC include cost savings through more efficient management, improved efficiency via a single view of all resources, and reduced risk by centralized access control and auditing. RMC automates resource discovery, allocation, monitoring, reporting, and budgeting. It helps match workloads with the best provisioning plan of on-demand, reserved, or spot resources based on requirements, budget, flexibility needs, and reliability constraints. Various scheduling and load balancing techniques can also improve quality of service by reducing wait times and increasing availability and performance when distributing tasks across servers.
Similar to Site reliability engineering - Lightning Talk (20)
Design patterns and plan for developing high available azure applications
Design patterns and plan for developing high available azure applications
Performance Testing Strategy for Cloud-Based System using Open Source Testing...
Performance Testing Strategy for Cloud-Based System using Open Source Testing...
S.R.E - create ultra-scalable and highly reliable systems
S.R.E - create ultra-scalable and highly reliable systems
typesofperformancetesting-130505055525-phpapp02.pdf
typesofperformancetesting-130505055525-phpapp02.pdf
Top Business Benefits of Application Lifecycle Management (ALM)
Top Business Benefits of Application Lifecycle Management (ALM)
Cloudbyz ppm, integrated enterprise ppm-alm-apm on force.com
Cloudbyz ppm, integrated enterprise ppm-alm-apm on force.com
Recently uploaded
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Infrastructure Challenges in Scaling RAG with Custom AI models
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Recently uploaded (20)
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Infrastructure Challenges in Scaling RAG with Custom AI models
Infrastructure Challenges in Scaling RAG with Custom AI models
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Site reliability engineering - Lightning Talk
- 1. PROPRIETARY AND CONFIDENTIAL Site Reliability Engineering Michael Blakeney
- 2. "an SRE team is responsible for the availability, latency, performance, efficiency, change management, monitoring, emergency response, and capacity planning of their service(s)." What is SRE? • Ensuring a Durable Focus on Engineering • Pursuing Maximum Change Velocity Without Violating a Service’s SLO • Monitoring • Emergency Response • Change Management • Demand Forecasting and Capacity Planning • Provisioning • Efficiency and Performance
- 3. PROPRIETARY AND CONFIDENTIAL Availability Time Based Aggregate Based 3 "If you haven't tried it, assume it's broken" Too binary for distributed systems that can enter partial downtime or degraded states Much broader and able to capture user facing experience more effectively
- 4. Service Level Indicators Service Level Objectives Service Level Agreement SLI, SLO, SLA Database state should be 100% recovered in no more than 1 day. "99% of pipeline runs cover 100% of the data." 90% ( averaged over 1 minute ) of http requests to the backend should complete in less than 10ms 4 https://landing.google.com/sre/workbook/chapters/slo-document/
- 5. PROPRIETARY AND CONFIDENTIAL the time it takes for your service to process a request Four Golden Signals 5 Latency the measurement of the requests the service is handling Traffic the request rate of errors Errors How much a resource with limited quantity is utilized, usually measured as a Percentage of that resource Saturation
- 6. PROPRIETARY AND CONFIDENTIAL Error Budgets • Error budgets enable teams to make objective decisions regarding prioritization of features versus reliability. • Given an availability target the error budget defines the tolerable amount of service unavailability. i.e. 99.99% availability => 0.01% unavailability or 12.96 minutes per quarter https://landing.google.com/sre/sre-book/chapters/availability-table/ https://landing.google.com/sre/workbook/chapters/error-budget-policy/ 6 "Ways in which things go wrong are special cases of the ways in which things go right"
- 7. PROPRIETARY AND CONFIDENTIAL Being Agile with SLOs • Transparency - the SLO and error budget policies along with all other relevant material should be made available to the team and stake holders • Inspection - the team should regularly review and analyze the effectiveness and relevancy of the policies • Adaptation - The team should be willing to adjust the policies so as to maximize the value delivered to customers. 7