Serverless Ops: What to Do / This is What We Do, When the Server Goes Away

Website Maintenance Alert

Due to scheduled maintenance, the USENIX website will not be available on Tuesday, December 17, from 10:00 am to 2:00 pm Pacific Daylight Time (UTC -7). We apologize for the inconvenience.

If you are trying to register for Enigma 2020, please complete your registration before or after this time period.

Wednesday, October 31, 2018 - 4:15 pm4:45 pm

Tom McLaughlin, ServerlessOps

Abstract: 

With the rise of serverless architecture, many of the common day-to-day operations tasks will change dramatically, if not disappear completely. We as Operations professionals will be challenged to redefine our roles and responsibilities within the technology organization as serverless abstracts away the server and its respective OS to cloud service providers. No stranger to this scenario, we will not only be tasked with solving these engineering obstacles introduced by the new serverless paradigm, but we will also need to prove our value to the business in the face of a changing technology landscape… again.

This is a combination professional/cultural and technical talk. We’ll start by discussing the disruption that serverless presents to operations and why. While DevOps and public cloud are becoming commonplace, serverless is the beginning of a new disruption cycle. We need to understand why serverless is disruptive and learn from the lessons of the past.

The talk will continue on to discuss the value of operations work and understanding the relationship between work and value. Not all work has the same value and we need to understand this so we prioritize the best use of our time.

Finally I will walk through the current state of serverless engineering and tools, and show how and where we fit in. For our career longevity and security we need to understand how we fit.

A few areas I’ll discuss include:

  • DevOps and public cloud… And how serverless is starting a new disruption cycle 10 years later.
  • Understanding and determining the value of your work
  • Moving up the value chain and closer to customer success metrics.
  • Team reorganization to better align with business success.
  • Serverless architectural decision making
  • Performance management and cost containment
  • Failure monitoring and service handling
  • Security risk and concerns

If you’re an Operations engineer and you had all your host and OS related work removed from you, would you know what to do to stay busy and demonstrate your value to your organization?

Tom McLaughlin, ServerlessOps

Tom is the founder of ServerlessOps and an experienced operations engineer. He started ServerlessOps after he asked the question, what would he do if servers went away? At a loss for an answer and interested in the future of his profession, he decided to pursue the answer. Tom is actively engaged in promoting serverless infrastructure and engaging with the community to learn more about their thoughts, wants, and concerns are around the topic.

Open Access Media

USENIX is committed to Open Access to the research presented at our events. Papers and proceedings are freely available to everyone once the event begins. Any video, audio, and/or slides that are posted after the event are also free and open to everyone. Support USENIX and our commitment to Open Access.

BibTeX
@conference {221792,
author = {Tom McLaughlin},
title = {Serverless Ops: What to Do / This is What We Do, When the Server Goes Away},
year = {2018},
address = {Nashville, TN},
publisher = {{USENIX} Association},
month = oct,
}

Presentation Video 

Presentation Audio