22. SREcon
22
• Темы:
• site reliability
• systems engineering
• complex distributed systems
• Компании:
• Google, Microsoft, Facebook, Linkedin, Ebay, Booking,
Netflix, Spotify, Uber, …
23. Доклады
23
• “Keys to SRE”, Ben Treynor, Site Reliability Tsar,
Google
• “Notes from Production Engineering”, Pedro
Canahuati, VP Production Engineering, Facebook
24. Facebook
24
Production Engineers at Facebook are hybrid
software/systems engineers who ensure that
Facebook's services run smoothly and have the
capacity for future growth. They are embedded in
every one of Facebook's product and infrastructure
teams, and are core participants in every significant
engineering effort underway in the company.
29. SRE Book
29
DevOps or SRE?
“One could view DevOps as a generalisation of
several core SRE principles to a wider range of
organisations, management structures, and
personnel.”
“One could equivalently view SRE as a specific
implementation of DevOps with some idiosyncratic
extensions.”
30. Ben Treynor, VP of
Google Engineering
30
We’ve iterated to the current SRE definition over the
last 15 years…
I expect we’ll continue to evolve it to make the role
even more attractive to developers while at the same
time making it more effective at running efficient, high
availability, large scale systems.
33. DevOps Handbook
33
• Методология, а не профессия
• С чего начать
• 3 пути:
• Практики непрерывной поставки (Dev -> Ops)
• Практики быстрой обратной связи (Ops -> Dev)
• Практики непрерывного обучения
50. SREcon
50
• Security and SRE
• Building Successful SRE in Large Enterprises
• Security as a Service
• The Evolution of Site Reliability Engineering
52. StackOverflow
52
DevOps and machine learning are important trends in
the software industry today. Languages and
frameworks associated with these kinds of works are
on the rise, and developers working in these areas
command the highest salaries.
SRE - ?
58. Википедия
58
• Site Reliability Engineering
• DevOps vs SRE
• SRE and DevOps share the same
foundational principles. SRE is viewed by
many (as cited in the Google SRE book) as a
"specific implementation of DevOps with
some idiosyncratic extensions."
61. Seeking SRE
61
• How to Apply SRE Principles without Dedicated SRE Teams
• The Intersection of Reliability and Privacy
• The Art and Science of the SLO (Service Level Objectives)
• Immutable Infrastructure and SRE
• Scriptable Load Balancers
• The Service Mesh: Wrangler of Your Microservices?
• Psychological Safety in SRE
62. How to Apply SRE Principles
without Dedicated SRE Teams
62
• SoundCloud (~100 engineers)
• Hired a couple of former Google SREs and tried
“SRE by the book”
• “We could not just copy Google SRE verbatim, we
had to adjust the approach to our circumstances.”
• SRE Team -> Embedded SRE -> True DevOps ->
Platforms Team -> Production Engineering
64. How SRE relates to
DevOps
64
“If you think of DevOps as a philosophy and an approach to working”
“SRE implements some of the philosophy that DevOps describes”
“SRE Engineer is closer to a concrete definition of a job or role than,
say, “DevOps engineer.”
“SRE has more concrete suggestions on how to change your work
practices earlier on in that journey, albeit requiring specific
adaptation. DevOps, having a wider focus, is somewhat more difficult
to reason about and translate into concrete steps, but precisely because
of that wider focus, is likely to meet with weaker initial resistance.”
72. Книги
72
• Переводы книг DevOps Handbook и SRE
выходят летом
• Есть переводы книг Проект Феникс и
Философия DevOps
73. Конференции
73
• DevOps: РИТ, Highload, DevOops, DevOpsPro,
DevOpsDays
• Как SRE следит за стабильностью и скоростью
HeadHunter (Антон Иванов)
• Отдельный отдел (разработчики)
• Про приложения и архитектуру
• Про мониторинг и дежурства
74. Наш опыт
74
• Есть DevOps, но не называют это DevOps
• Есть SRE, но не называют это SRE
• Есть DevOps инженеры
• Нет DevOps/SRE
75. Итого
75
• DevOps и SRE активно развиваются
• SRE инженер = DevOps инженер
• Только SRE недостаточно
• DevOps шире, поэтому сложнее для внедрения
• DevOps популярнее и скорее всего про вас
76. Итого
76
• DevOps и SRE активно развиваются
• SRE инженер = DevOps инженер
• Только SRE недостаточно
• DevOps шире, поэтому сложнее для внедрения
• DevOps популярнее и скорее всего про вас
77. Что не следует делать
77
• Скопипастить, не подумав
• Переименовываться в SRE
• Создавать отдельную SRE команду
78. Что следует делать
78
• Понять какую проблему вы решаете
• Понять какие проблемы решает DevOps и SRE
• Подумать как это поможет вам
• Обсудить/продать внутри компании