Course Outline
Introduction
- Integration of traditional information technology infrastructure with software development lifecycles.
- The necessity for automated processes and comprehensive observability within government systems for government operations.
- Distinguishing the responsibilities of software engineers from those of system administrators.
- Comparing the roles of Site Reliability Engineers versus DevOps practitioners.
Overview of an IT System
- System architecture considerations, including on-premises and cloud-based environments.
Overview of SRE Principles and Practices
- Infrastructure as Code methodologies.
- The application of containerization and orchestration technologies, such as Docker and Kubernetes.
- Continuous Integration, Continuous Deployment, and Continuous Delivery pipelines.
- Principles of system observability.
Evaluating an IT System
- Assessment of team capabilities and organizational resources.
- Documentation of existing systems and operational processes.
- Estimation of the potential impact of implementing Site Reliability Engineering practices.
- Responsibilities of the software engineering team.
- Responsibilities of the operational support team.
- Strategic oversight and decision-making by management.
Maintaining the Reliability of a System
- Definition and measurement of target service reliability.
- Understanding Service Level Objectives (SLOs).
- Clarification of Service Level Indicators (SLIs) and Service Level Agreements (SLAs).
- Management of error budgets.
- Development and implementation of SLOs.
Optimizing System Administration
- Establishment of development environments.
- Evaluation of Site Reliability Engineering tools.
- Prioritization of tasks for automation efforts.
- Software development practices.
Deploying "Infrastructure as Code"
- Testing and iterative refinement of code.
- Engineering systems to be anti-fragile and resilient.
- Post-incident analysis and learning from failures.
Monitoring a System
- Continuous observation of system performance metrics.
- Application of Site Reliability Engineering tools and techniques.
The Future of SRE
Summary and Conclusion
Requirements
- Foundational knowledge of information technology (IT) infrastructure.
- Familiarity with the software development lifecycle.
- Hands-on experience programming or scripting in at least one language.
Target Audience
- Software Developers
- System Administrators
- Software Architects
- DevOps Engineers
- IT Management Personnel
Testimonials (7)
How detailed subjects are explained with real world examples
Brian Hlabane - African Bank
Course - Site Reliability Engineering (SRE) Fundamentals
She is expert in area and provide really nice training. Material, training was really mix of examples , discussion and
Peter Tutka - Deutsche Telekom IT & Telecommunications Slovakia s.r.o.
Course - Site Reliability Engineering (SRE) Fundamentals
View on the SRE/ DevOps from more business/ theoretical point of view. Most helpful for people who already have the practical view.
Michael Varhol - Deutsche Telekom IT & Telecommunications Slovakia s.r.o.
Course - Site Reliability Engineering (SRE) Fundamentals
Approach of the training to send questionnaire before the training, so the training was planned accordingly to expectations. Brings the participants more active.
Stefan Girman - Deutsche Telekom IT & Telecommunications Slovakia s.r.o.
Course - Site Reliability Engineering (SRE) Fundamentals
Sticking to the initial survey from attendees about what should be the focus of training.
Denis Majorsky - Deutsche Telekom IT & Telecommunications Slovakia s.r.o.
Course - Site Reliability Engineering (SRE) Fundamentals
discussions , SRE definition
Daniel Horvath - Deutsche Telekom IT & Telecommunications Slovakia s.r.o.
Course - Site Reliability Engineering (SRE) Fundamentals
Concept of the training, keeping the people focused by asking them a questions and triggering discussions. Also group breakout sessions were great to think about things in groups and see different outcomes from other group.
