Skip to content
The DevOps Loop

Ep 2: The DevOps infinity loop

Episode 2 of 448 · Concept

▶ Instagram

In one sentence: DevOps is drawn as an infinity loop because software is never “done”: you plan, build and ship, watch what happens, and use what you learn to plan the next change.

The 8 stages

Section titled “The 8 stages”

The left half is mostly Dev, the right half mostly Ops, but one team owns all of it.

  1. Plan: decide what to build next (a feature, a bug fix).
  2. Code: write the change and save it in Git.
  3. Build: turn the code into something that can run (a package or container image).
  4. Test: automated tests check nothing broke.
  5. Release: mark a version as ready to go out.
  6. Deploy: put that version on the servers.
  7. Operate: keep it running: scaling, backups, updates.
  8. Monitor: watch errors, speed and usage, then feed what you learn back into Plan.

Why a loop and not a line?

Section titled “Why a loop and not a line?”

A line ends. A loop keeps going. Each trip around the loop should be small and fast: a small change is easy to test, easy to deploy and easy to undo if something goes wrong.