OpsLevel Logo
Product

Visibility

Catalog

Keep an automated record of truth

Integrations

Unify your entire tech stack

AI Engine

Restoring knowledge & generating insight

Standards

Scorecards

Measure and improve software health

Campaigns

Action on cross-cutting initiatives with ease

Checks

Get actionable insights

Developer Autonomy

Service Templates

Spin up new services within guardrails

Self-service Actions

Empower devs to do more on their own

Knowledge Center

Tap into API & Tech Docs in one single place

Featured Resource

Click-through Tour: OpsLevel Overview
Click-through Tour: OpsLevel Overview
Read more
Use Cases

Use cases

Improve Standards

Set and rollout best practices for your software

Drive Ownership

Build accountability and clarity into your catalog

Developer Experience

Free up your team to focus on high-impact work

Featured Resource

The Ultimate Guide to Microservices Versioning Best Practices
The Ultimate Guide to Microservices Versioning Best Practices
Read more
Customers
Our customers

We support leading engineering teams to deliver high-quality software, faster.

More customers
Hudl
Hudl goes from Rookie to MVP with OpsLevel
Read more
Hudl
Keller Williams
Keller Williams’ software catalog becomes a vital source of truth
Read more
Keller Williams
Duolingo
How Duolingo automates service creation and maintenance to tackle more impactful infra work
Read more
Duolingo
Resources
Our resources

Explore our library of helpful resources and learn what your team can do with OpsLevel.

All resources

Resource types

Blog

Resources, tips, and the latest in engineering insights

Guide

Practical resources to roll out new programs and features

Demo

Videos of our product and features

Events

Live and on-demand conversations

Interactive Demo

See OpsLevel in action

Pricing

Flexible and designed for your unique needs

Docs
Log In
Book a demo
Log In
Book a demo
No items found.
Share this
Table of contents
 link
 
Resources
Blog

Taking Back DevOps

Insights
DevX
Tooling
DevOps
Taking Back DevOps
John Laban
|
November 18, 2020

Let’s get DevOps to mean Service Ownership again.

We broke DevOps. And it’s preventing us from building.

When the first cloud providers emerged in the mid-2000s, they unlocked a new superpower: the ability to near-instantly provision hardware. Service-oriented architecture and microservices developed as a new architectural pattern. As a result, DevOps emerged as a practice to organize engineering teams around those new services - combining development and operations responsibilities onto the same team.

In 2006, Werner Vogels, CTO at Amazon, described DevOps as: “You build it, you run it.” Fast forward to today and DevOps is a far cry from these origins. Code is no longer deployed efficiently, and the practice of DevOps has weakened. Here’s how this happened:

1. We rendered the term DevOps meaningless.

Over the last several years, DevOps has become simultaneously a practice, a culture, a team, a job title, and a vendor product. You can hire some DevOps, buy some DevOps, adopt DevOps, and sprinkle a little bit of DevOps on top for good measure.

  • ‘DevOps’ is a team, responsible for horizontal engineering concerns like standardized CI/CD and observability.
  • ‘DevOps’ is a trendy job title, merely renamed from “Operations”.
  • ‘DevOps’ is a vendor product, like “Azure DevOps”, “ServiceNow Enterprise DevOps”, and “IBM DevOps”.

2. We spent way too much time debating microservices vs monolith.

This is the wrong debate. And it’s distracted teams from focusing on how to own and operate code efficiently. For some companies, a monolith works just fine. For others, microservices is the way to go. For many, it’s a hybrid of fat services or serverless or applications or some other mix. The more important question is: How do you get your team to a place where engineers own the code they write so everyone can ship faster and safer?

3. We built some DevOps tools, but for crucial needs we’re stuck in spreadsheets.

DevOps tools are siloed around monitoring, logging, tracing, incident management, CI/CD, etc. But there is nothing that unifies the information from those tools to answer broad questions about production architecture. Companies with the best DevOps cultures use this set of siloed tools, but they have also spent millions of dollars to build their own tools and systems–everything from lists of owners to full-fledged internal tools. We’ve seen teams with:

  • Giant wikis of services that answer basic questions about architecture, including simply who owns what.
  • Spreadsheets of services that are painstakingly created (and later tossed away) during engineering initiatives like upgrades or security improvements across a large and complex architecture.
  • Eventually spreadsheets and wikis are thrown away and complex internal tools are created that require a lot of engineering resources to build and maintain.

Building these stop-gap solutions are a huge barrier to entry; there needs to be a way for all teams to adopt DevOps culture.

Let’s take back DevOps.

If we want to get back to shipping code even faster, more securely, and with less risk, we need to reset DevOps so that it’s synonymous with Service Ownership.

When DevOps = Service ownership, teams get:

  • Autonomy: Teams fully control how their systems are built and run in production. Architecture becomes less prescriptive.
  • Speed: As long as your team’s SLOs are being met, there should be nothing stopping you from shipping quickly.
  • Resiliency: Shifting reliability and security concerns to dev teams naturally increases risk, but ownership involves educating/measuring teams against critical practices so that they can still deploy with low risk.
  • Accountability: People are no longer paged because a service goes haywire - or, worse yet, has a security breach - and learn that nobody owns the service, wants to touch it, or even knows anything about it.

We’ve underinvested in tools to make DevOps actually work. There’s a lot we still need to build to help engineering teams adopt service ownership and unlock the full power of DevOps.

__________________________________

OpsLevel enables Service Ownership. It’s the future of DevOps.

OpsLevel helps DevOps teams own, operate, and understand their entire production infrastructure. You can easily catalog all your services, tools, ownership, and changes, while you continuously measure and improve how you build and operate your software. Teams ship faster, with confidence.

Forward-thinking engineering teams at Segment, Zapier, Auth0, Convoy, Under Armour, Chegg, and more use OpsLevel to drive service ownership. We’re proud to announce we’ve raised $5M in funding led by Vertex Ventures, with participation from S28 Capital, Webb Investment Network, Union Capital, and a number of angels including:

  • Alex Solomon, Andrew Miklas, and Baskar Puvanathasan (founders of PagerDuty)
  • Anne Raimondi (CCO of Guru, Board member Asana, Gusto, Patreon)
  • Frederic Kerrest (Executive Vice Chairman, COO, and co-founder of Okta)
  • Jean-Michel Lemieux (CTO of Shopify)
  • Maynard Webb (ex-COO of eBay)
  • Yuri Sagalov (co-founder of AeroFS)
  • Evan Weaver (CTO and co-founder of Fauna)
  • Paul Judge (co-founder of Pindrop Security)
  • Bill Clerico (co-founder of WePay)

If you’re interested in joining our mission to take back DevOps and empower cultures of service ownership, check out our open roles.

John Laban and Ken Rose are co-founders of OpsLevel. John was previously PagerDuty’s first engineer and the pair of them bring senior technical expertise from Shopify, Amazon, and more.  They’ve spent the last decade scaling engineering teams and helping them transition to DevOps and service ownership.

More resources

Fast code, firm control: A leadership report on AI coding adoption
Blog
Fast code, firm control: A leadership report on AI coding adoption

AI is writing your code; are you ready?

Read more
March Product Updates
Blog
March Product Updates

Some of the big releases from the month of March.

Read more
How Generative AI Is Changing Software Development: Key Insights from the DORA Report
Blog
How Generative AI Is Changing Software Development: Key Insights from the DORA Report

Discover the key findings from the 2024 DORA Report on Generative AI in Software Development. Learn how OpsLevel’s AI-powered tools enhance productivity, improve code quality, and simplify documentation, while helping developers avoid common pitfalls of AI adoption.

Read more
Product
Software catalogMaturityIntegrationsSelf-serviceKnowledge CenterBook a meeting
Company
About usCareersContact usCustomersPartnersSecurity
Resources
DocsEventsBlogPricingDemoGuide to Internal Developer PortalsGuide to Production Readiness
Comparisons
OpsLevel vs BackstageOpsLevel vs CortexOpsLevel vs Atlassian CompassOpsLevel vs Port
Subscribe
Join our newsletter to stay up to date on features and releases.
By subscribing you agree to with our Privacy Policy and provide consent to receive updates from our company.
SOC 2AICPA SOC
© 2024 J/K Labs Inc. All rights reserved.
Terms of Use
Privacy Policy
Responsible Disclosure
By using this website, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Data Processing Agreement for more information.
Okay!