C
DevOps//Lesson 01

DevOps

30 min·theory

DevOps

🎯 After reading this lesson

After completing this lesson, you will be able to confidently handle the following three things.

  • ✅ Infrastructure patterns in "DevOps" (development + operations automation)
  • ✅ Operational pitfalls + monitoring (CI/CD (automated build & deploy), Docker (container tooling))
  • ✅ Frequently asked interview questions (Kubernetes (k8s, automated container management), IaC (Infrastructure as Code))

Keep the learning objectives as a checklist, and close the lesson once you can answer all of them.

👨‍💻 4 People Who Built DevOps — From Coining the Term to Containers & Kubernetes

01
Patrick DeboisPatrick Debois
Coined the term 'DevOps'Independent Consultant1969~Present

The person who brought 'DevOps' into the world — the beginning of a conference that broke down the wall between operations and development

  • 2007 Experienced firsthand the inefficiencies of Dev/Ops separation on a Belgian government project
  • 2009 Hosted the first DevOpsDays conference in Ghent, Belgium — spreading the term 'DevOps'
  • 2010 The DevOpsDays movement gained global momentum — organizing communities worldwide
  • 2015 Co-authored The DevOps Handbook — accelerating adoption of DevOps practices
DevOpsDays & the cultural movement — the origin of the integrated dev/ops mindsetDEVOPS · Term Coiner
02
Solomon HykesSolomon Hykes
Creator of DockerdotCloud → Docker Inc.1983~Present

The person who packaged Linux kernel features together to make 'containers' accessible to everyone

  • 2010 Born in France, co-founded dotCloud (a PaaS startup)
  • 2013 Publicly unveiled Docker at PyCon — launching the container revolution
  • 2014 Renamed the company from dotCloud to Docker Inc. and began full commercialization
  • 2018 Resigned as Docker Inc. CTO — founded Dagger to advance CI/CD evolution
Container standardization — the starting point of the Kubernetes, serverless, and MSA eraDOCKER · Container Originator
03
Joe BedaJoe Beda
Co-creator of KubernetesGoogle → Heptio → VMwareCurrently Active

Co-creator who brought Google's internal Borg experience to the open-source project Kubernetes

  • 2004 Joined Google after Hyperic — contributed to infrastructure systems development
  • 2014 Launched the Kubernetes project alongside Brendan Burns and Craig McLuckie
  • 2016 Co-founded Heptio — provided enterprise Kubernetes adoption consulting
  • 2018 Heptio acquired by VMware — joined as a core architect of VMware Tanzu
Kubernetes — the de facto standard for container orchestrationKUBERNETES · Co-founder
04
Kelsey HightowerKelsey Hightower
Kubernetes Educator & AdvocateGoogle Cloud → IndependentCurrently Active

The evangelist who awakened engineers worldwide by having them install Kubernetes 'bare-handed'

  • 2015 Joined Google Cloud via CoreOS — began evangelizing Kubernetes worldwide
  • 2016 Published 'Kubernetes the Hard Way' guide — established as a key learning resource
  • 2018 Keynoted conferences around the world — shaping Kubernetes operational patterns
  • 2023 Announced departure from Google and retirement — continued as an independent community mentor
Establishing Kubernetes education & practical patterns — the person who placed 'culture' on top of the toolingK8S ADVOCATE · Evangelist·Educator
👥
In a nutshell
Debois (term & culture) → Hykes (Docker) → Beda (Kubernetes) → Hightower (evangelism). These four people laid the foundation of modern DevOps infrastructure.

Why You Need to Understand DevOps

In a nutshell: Automating every step from writing code → to getting it into users' hands. Deployment speed = business speed.


Tool Mapping

AreaStandards
ContainerDocker · Podman (run apps in isolated boxes)
OrchestrationKubernetes (k8s) (automated container management) · Docker Swarm
CI/CD (automated build & deploy)GitHub Actions · Jenkins · GitLab CI
IaC (Infrastructure as Code)Terraform (infrastructure definition tool) · Pulumi · AWS CDK
CloudAWS · GCP · Azure (services that let you rent servers)
MonitoringPrometheus · Grafana · Datadog · OpenTelemetry (observability data standard)
Developer PortalBackstage (service catalog & documentation hub)

5 Core Reasons

ReasonMeaning
Containers (Docker)Permanently solves the 'it works on my machine' problem
CI/CD (automated build & deploy)git push → automated test, build, and deploy. Fewer human errors
IaC (Infrastructure as Code)Infrastructure as code — reproducible, version-controlled, and rollback-ready
Monitoring (SRE (Site Reliability Engineering))Detect issues via alerts before users report them. Track DORA (4 metrics: deployment frequency, failure rate, etc.)
K8s (Kubernetes, automated container management)Auto-scaling when traffic spikes. Auto-recovery when a server goes down. blue-green (switch between two environments) · canary (send a subset of traffic first) strategies

Key takeaway: Even small companies that ignore DevOps end up with manual deploys → incidents → late nights. Automation is a survival tool.

🤖 Try Asking AI Like This

Once you understand the concepts in this lesson, you can give AI specific instructions.

  • "Optimize the Dockerfile (container image spec file) for this Node app using a multi-stage build. Include alpine + .dockerignore."
  • "Create a docker-compose.yml (multi-container definition) for PostgreSQL + Redis + app containers, and add a healthcheck (status check)."
  • "Write a GitHub Actions (automated build & deploy workflow) yml (lint → test → image build → deploy)"
  • "Stage this deployment using a canary (send a small portion of traffic first) strategy"

Why This Reduces Tokens

If you don't know DevOps vocabulary (image, layer, health check, rolling deployment) and just say 'deploy this,' the AI will ask you to clarify the environment first. Learn the vocabulary once and you can generate yml right away.

DevOps - DevOps