Currently Empty: $0.00
DevOps
The DevOps Periodic Table & Core Components Explained
Legendary Ways Academy · Foundations
The DevOps Periodic Table, Mapped Out
Every major category of DevOps tooling, source control, CI/CD, IaC, monitoring, security, in one clear map, so you understand where each tool actually fits before you pick one.
8 categories
Real examples per box
No vendor bias
The “DevOps periodic table” is a popular way of visualizing the tooling landscape as a grid of categories, echoing the chemistry periodic table’s grouping of elements by shared properties. The specific tools inside each category change constantly as the market evolves, but the categories themselves have stayed remarkably stable, which is what makes this framing useful: understand the eight categories below and you can slot in any new tool you encounter, rather than treating each new product name as an isolated thing to memorize.
The Core Categories
Plan
Work tracking and project management, Jira, Linear, Azure Boards. Covered in our DevOps vs. Jira explainer.
Source Control
Version control and code review, Git, hosted on GitHub, GitLab, or Bitbucket, with branch protection and pull request workflows.
CI/CD
Build, test, and deployment automation, GitHub Actions, Jenkins, GitLab CI, CircleCI. Full breakdown in our CI/CD tools guide.
Infrastructure as Code
Declarative infrastructure provisioning, Terraform, OpenTofu, Pulumi, CloudFormation.
Container Orchestration
Running containerized workloads at scale, Kubernetes, along with managed variants like EKS, AKS, and GKE.
Configuration Management
Automating server and application configuration, Ansible, Chef, Puppet, increasingly overlapping with container-based approaches.
Monitoring & Observability
Metrics, logs, and traces, Prometheus, Grafana, Datadog. Full detail in our monitoring guide.
Security
Vulnerability scanning, secrets management, and policy enforcement integrated into the pipeline, covered in our security best practices guide.
Why Categories Matter More Than Specific Tool Names
A common mistake for people new to the field is trying to learn every popular tool by name rather than understanding what category each one belongs to and what problem that category solves. This backfires because tool popularity shifts (today’s leading CI/CD platform may not be tomorrow’s), while the underlying category and its purpose stays constant. Someone who understands “CI/CD tools automate build, test, and deploy” can pick up any new tool in that category quickly, since the mental model transfers; someone who only memorized “GitHub Actions does X” has to relearn from scratch when a team uses Jenkins instead.
This categorical understanding is also what interviewers are often really testing when they ask about specific tools: not whether you’ve used that exact product, but whether you understand what role it plays in a delivery pipeline and could reason about an unfamiliar tool in the same category.
How the Categories Connect in a Real Pipeline
These categories aren’t independent silos; a real DevOps toolchain wires them together end to end. A commit in Source Control triggers a CI/CD pipeline, which runs tests, builds a container image, and deploys infrastructure defined through Infrastructure as Code onto a Container Orchestration platform, all while Monitoring tools watch the result and Security scanning runs at multiple stages along the way. Our tool ecosystem integrations guide covers exactly how these pieces typically connect via APIs, webhooks, and shared configuration.
Two Categories Often Missing From Simpler Versions of This Map
Simpler versions of the DevOps periodic table circulating online sometimes stop at six categories, leaving out two that have become increasingly important in mature organizations. Cost management (FinOps-adjacent tooling like AWS Cost Explorer, Kubecost, and Azure Cost Management) has grown into its own category as cloud spend has become large enough at most companies to require dedicated visibility and optimization tooling, not just an afterthought bundled into general monitoring. Artifact and package management (Artifactory, Nexus, or cloud-native registries) is another frequently overlooked category, covering how build outputs, container images, and internal packages get stored, versioned, and distributed, distinct from source code itself.
Including these two in your mental map matters practically because job postings increasingly list them as distinct requirements, and because skipping them in a self-taught learning path leaves a real gap that shows up in interviews or on the job when a team’s cost or artifact management practices come up.
Frequently Asked Questions
Do I need to learn a tool from every category to get a DevOps job?
Not all at once. Most entry-level roles expect solid competence in one or two categories (commonly CI/CD and basic IaC) with working familiarity across the rest, deepening over time on the job.
Which category should I learn first?
Source control and CI/CD fundamentals first, since nearly every other category assumes you already understand how code moves from a commit to a deployed environment.
Are some categories more important than others?
Not universally; importance depends on the specific role and company. A security-focused DevOps role weighs the Security category heavily; a platform engineering role may weigh Infrastructure as Code and Container Orchestration more.
Does AI change any of these categories?
It’s adding new capability within existing categories (smarter monitoring anomaly detection, AI-assisted IaC generation) rather than replacing the categories themselves; see our AI in DevOps guide for specifics.
Related reading: see the full CI/CD tools guide, review tool ecosystem integrations, or check our security best practices guide.