Slides from Eric Richard's presentation on how HubSpot is Rethinking DevOps. Presented to the MassTLC CTO & VP of Engineering Peer Group 9/23/15

1. Ops-ting Out:
How HubSpot Is Rethinking DevOps
Eric Richard
VP Engineering, HubSpot

2. What is DevOps?

3. The old model…
Developers wrote code.
IT teams managed the systems.

4. The old model…
Developers wrote code.
IT teams managed the systems.
They got paged at 2AM to fix things
(even if they didn’t break them).

5. The alignment between responsibility
and accountability was BROKEN.

6. Dev Ops

7. There was a divide between
developers and IT teams
that led to slow release
cycles and negative
relationships.

8. The new model…
Developers are responsible for the
operations system of their piece
of the app.

9. The new model…
Developers are responsible for the
operations system of their piece
of the app.
at HubSpot

10. But how does this work?

11. We invest heavily in
tooling and infrastructure…

12. Build extremely resilient infrastructure to minimize the infrastructural
outages that Ops normally handles. The best way to avoid the pain
of your team being paged is to make the pagers never happen.1

13. Provide developers with strong tooling so that they can easily
manage the infrastructure. This doesn't mean turning them into
experts, but giving them control over that which they should control.2

14. Use Ops as a 2nd line of support to developers
in the event that the steps weren't sufficient.3

15. Responsibility and accountability are aligned.

16. Looking ahead…
• Can we extend our use of Mesos to
other systems (MySQL, Kafka,
HBase)?
• Can we develop self-healing systems
that automate manual processes?

17. Thank You!