Ops-ting Out: How HubSpot Is Rethinking DevOps

Eric Richard VP Engineering, HubSpot

What is DevOps?

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

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).

The alignment between responsibility and accountability was BROKEN.

Dev Ops

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

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

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

at HubSpot

But how does this work?

We invest heavily in tooling and infrastructure…

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

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

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

Responsibility and accountability are aligned.

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?

Thank You!