Get in Touch

Course Outline

Introduction

  • How SRE integrates traditional IT with software development.
  • The necessity of automation and observability.
  • The distinction between software engineers and system administrators.
  • Site Reliability Engineers versus DevOps engineers.

Overview of an IT System

  • System architecture, covering on-premise and cloud environments.

Overview of SRE Principles and Practices

  • Infrastructure as Code.
  • The role of containerization and orchestration (Docker, Kubernetes, etc.)
  • Continuous Integration, Continuous Deployment, and Continuous Delivery.
  • Observability.

Evaluating an IT System

  • Assessing team and organizational resources.
  • Mapping out systems and processes.
  • Estimating the potential impact of SRE.
  • The role of the software engineering team.
  • The role of the operational team.
  • The role of management.

Maintaining System Reliability

  • Describing and measuring desired service reliability.
  • Understanding Service Level Objectives (SLOs).
  • Understanding Service Level Indicators (SLIs) and Service Level Agreements (SLAs).
  • Working with Error Budgets.
  • Developing an SLO.

Optimizing System Administration

  • Setting up a development environment.
  • Evaluating SRE tools.
  • Prioritizing tasks for automation.
  • Writing software.

Deploying "Infrastructure as Code"

  • Testing and iterating code.
  • Making a system anti-fragile.
  • Learning from failure.

Monitoring a System

  • Observing system performance.
  • SRE tools and techniques.

The Future of SRE

Summary and Conclusion

Requirements

  • A basic understanding of IT infrastructure.
  • A general knowledge of the software development lifecycle.
  • Experience programming or scripting in any language.

Audience

  • Developers
  • System administrators
  • Software Architects
  • DevOps engineers
  • IT Managers
 21 Hours

Testimonials (7)

Related Categories