Case Study

PagerDuty's Nomadic journey

Explore PagerDuty's story of adopting Nomad and what is involved in adopting Nomad as your container scheduler.

Adopting a container scheduler is a daunting task, with its as-yet unknown failure modes, quirky preferences, and opinionated UX. How will we know if it stops behaving? What even is normal behaviour?

How will developers interact with it? How will it integrate with our existing monitoring tools and network, and how long will it take to figure these things out? These uncertainties spell risk for the critical production services that will be running on it and for the people who will be interacting with it day-to-day.

In this talk, Marguerite des Trois Maisons, SRE Software Developer & Product Owner at PagerDuty, shares their story of adopting Nomad: what they did, what went well, what went poorly, how long it took them, and areas for improvement in Nomad's usage story so that you can have a better idea of what is involved in adopting Nomad as your container scheduler.

More resources like this one

  • 1/19/2023
  • Presentation

10 Things I Learned Building Nomad-Packs

  • 12/31/2022
  • Presentation

All Hands on Deck: How We Share Our Work

  • 12/31/2022
  • Presentation

Launching the Fermyon Cloud with Nomad and WebAssembly

  • 12/31/2022
  • Presentation

Portable CD pipelines for Nomad with Vault and Dagger