DevOps reference data
DevOps practices, CI/CD, and infrastructure as code.
Topic guide
What DevOps covers
DevOps reference data covers the practices and tools that carry code from a commit to a running, observed service: version-control workflows, the stages of a CI/CD pipeline, infrastructure described as code, virtualized infrastructure, monitoring and logging, and the reliability practices of site reliability engineering. DevOps is a set of habits more than a product category, so the same tool names appear across many teams used in very different ways, and the useful question is what practice a tool supports.
Key ideas
- Continuous integration
- Merging small changes to a shared branch frequently and verifying each with an automated build and test run.
- Continuous delivery vs deployment
- Delivery keeps every change releasable with a manual release decision; deployment releases every passing change automatically.
- Infrastructure as code
- Describing servers, networks and services in versioned files so environments can be reviewed, reproduced and changed like software.
- SLI, SLO, SLA
- An indicator is a measurement, an objective is the target for it, and an agreement is the contractual commitment, often with penalties, built on top.
- Error budget
- The amount of unreliability an SLO allows. Spending it slows releases; having it left permits risk.
- Observability
- The ability to understand a system's internal state from its outputs: metrics, logs and traces.
- Blameless postmortem
- A review of an incident focused on system and process causes rather than individual fault.
Common pitfalls
- Buying tools before agreeing on the practice. A pipeline that nobody trusts, or alerts that nobody acts on, adds work without safety.
- Setting an SLO of 100%. It is unreachable and leaves no budget for change; pick a target users actually need.
- Letting infrastructure drift from its code by making manual changes in production.
- Treating gitflow, trunk-based development or any workflow as universally correct instead of matching it to release cadence and team size.
Using it from an agent
- When explaining a pipeline, name the stage, the signal it produces and what failing it blocks.
- Recommend SLOs by user-visible behavior (latency, availability, correctness), not by internal metrics.
- For tool comparisons, state the category (metrics, logs, traces, IaC) first; many names are not like-for-like.
Start with: CI/CD Pipeline Stages · Site Reliability Practices
Datasets in DevOps
-
CI/CD Pipeline Stages
Typical stages in a continuous integration and delivery pipeline.
12 entries -
Infrastructure as Code Tools
Tools for managing infrastructure through code.
12 entries -
Monitoring and Logging Tools
Popular observability and telemetry tools.
14 entries -
Observability Signals and Alert Design
Operational signals, useful questions, and failure modes for service monitoring and incident diagnosis.
10 entries -
Site Reliability Practices
Key concepts from site reliability engineering.
16 entries -
Version Control Workflows
Common branching and collaboration workflows.
9 entries -
Virtualization Concepts
Key concepts in hardware virtualization and virtual machines.
13 entries
Fetch this category
One request returns the category with all of its dataset summaries. Append
?format=yaml or ?format=toon for the other encodings.
GET https://yjtoon.com/api/category/devops?format=json