Foray

Site Reliability Engineering roadmap

How to keep services dependable: measure reliability, respond to failure, learn from it and design systems that survive it.

11 topics · 61 nodes · 53 covered · 4 partly · 4 planned · updated 2026-10-17

Sign in with your Mycelium account to see which nodes you have finished.

Guided path: Site Reliability EngineeringHow to keep services dependable: measure reliability, respond to failure, learn from it and design systems that survive it.22 stages
  1. 1.Linux for DevOps: The Command Line, Services and TroubleshootingBeginner
  2. 2.Networking for DevOps: From Packets to ProductionBeginner
  3. 3.Bash Scripting: Automating the Command Line SafelyBeginner
  4. 4.Python for OperationsBeginner
  5. 5.Site Reliability EngineeringBeginner
  6. 6.Observability: Metrics, Logs, Traces and AlertingBeginner
  7. 7.Linux for DevOps: The Command Line, Services and TroubleshootingIntermediate
  8. 8.Site Reliability EngineeringIntermediate
  9. 9.Observability: Metrics, Logs, Traces and AlertingIntermediate
  10. 10.Release Strategies: Shipping Changes SafelyBeginner
  11. 11.Release Strategies: Shipping Changes SafelyIntermediate
  12. 12.Backup and Disaster RecoveryBeginner
  13. 13.Chaos EngineeringBeginner
  14. 14.Python for OperationsIntermediate
  15. 15.Site Reliability EngineeringAdvanced
  16. 16.Observability: Metrics, Logs, Traces and AlertingAdvanced
  17. 17.Backup and Disaster RecoveryIntermediate
  18. 18.Chaos EngineeringIntermediate
  19. 19.Linux for DevOps: The Command Line, Services and TroubleshootingAdvanced
  20. 20.Backup and Disaster RecoveryAdvanced
  21. 21.Chaos EngineeringAdvanced
  22. 22.FinOps: Cloud Cost ManagementBeginner
Show
  • Covered
  • Partly covered
  • Planned

  1. 1. Core

    Foundations of reliability

    What SRE is and why 100% is the wrong target.

    4 / 4 covered

  2. 2. Core

    Service levels

    Measuring what users experience and deciding what is good enough.

    4 / 5 covered

  3. 3. Core

    Monitoring and alerting

    Seeing problems early and paging only when it matters.

    6 / 6 covered

  4. 4. Core

    On-call and incident response

    Responding calmly, communicating clearly and learning afterwards.

    5 / 6 covered

  5. 5. Core

    Toil and automation

    Removing repetitive work so engineers can improve the system.

    3 / 5 covered

  6. 6. Recommended

    Capacity and performance

    Having enough, without paying for far more than you need.

    5 / 6 covered

  7. 7. Core

    Safe change

    Most outages follow a change, so make change small and reversible.

    6 / 6 covered

  8. 8. Core

    Resilience engineering

    Designing for partial failure and proving it works.

    5 / 6 covered

  9. 9. Core

    Data durability and disaster recovery

    Surviving the worst day.

    7 / 7 covered

  10. 10. Recommended

    Platform knowledge SREs lean on

    The systems underneath the services.

    6 / 6 covered

  11. 11. Optional

    Advanced reliability

    Going deeper once the basics are solid.

    2 / 4 covered