{ "api": "YAML JSON TOON Database", "version": "1.0.0", "format": "json", "category": { "id": 14, "slug": "devops", "name": "DevOps", "description": "DevOps practices, CI/CD, and infrastructure as code.", "icon": "terminal", "created_at": 1783090350, "topic": { "overview": "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": [ { "term": "Continuous integration", "meaning": "Merging small changes to a shared branch frequently and verifying each with an automated build and test run." }, { "term": "Continuous delivery vs deployment", "meaning": "Delivery keeps every change releasable with a manual release decision; deployment releases every passing change automatically." }, { "term": "Infrastructure as code", "meaning": "Describing servers, networks and services in versioned files so environments can be reviewed, reproduced and changed like software." }, { "term": "SLI, SLO, SLA", "meaning": "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." }, { "term": "Error budget", "meaning": "The amount of unreliability an SLO allows. Spending it slows releases; having it left permits risk." }, { "term": "Observability", "meaning": "The ability to understand a system's internal state from its outputs: metrics, logs and traces." }, { "term": "Blameless postmortem", "meaning": "A review of an incident focused on system and process causes rather than individual fault." } ], "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." ], "agent_tips": [ "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": [ "cicd-pipeline-stages", "site-reliability-practices" ] } }, "datasets": [ { "id": 1, "slug": "cicd-pipeline-stages", "title": "CI/CD Pipeline Stages", "description": "Typical stages in a continuous integration and delivery pipeline.", "tags": "devops,cicd,automation", "view_count": 0, "created_at": 1783090350, "entry_count": 12, "summary": "The stages a change passes through from source control to production and back as monitoring feedback: source, build, test, deploy, operate and monitor, plus planning, review, security scanning, packaging, release and rollback stages that mature pipelines add." }, { "id": 2, "slug": "infrastructure-as-code-tools", "title": "Infrastructure as Code Tools", "description": "Tools for managing infrastructure through code.", "tags": "devops,iac,terraform", "view_count": 0, "created_at": 1783090350, "entry_count": 12, "summary": "Tools for describing infrastructure as code: provisioning tools such as Terraform, CloudFormation and Pulumi, and configuration-management tools such as Ansible, Puppet and Chef, plus newer and adjacent entries such as OpenTofu, the AWS CDK, Crossplane, Packer and Bicep." }, { "id": 3, "slug": "monitoring-logging-tools", "title": "Monitoring and Logging Tools", "description": "Popular observability and telemetry tools.", "tags": "devops,monitoring,logging", "view_count": 0, "created_at": 1783090350, "entry_count": 14, "summary": "Observability tools by what they collect: metrics and dashboards (Prometheus, Grafana), logs (the ELK Stack, Loki), traces (Jaeger) and commercial platforms such as Datadog and New Relic, plus collectors, standards and error trackers like Fluent Bit, OpenTelemetry and Sentry." }, { "id": 1015, "slug": "observability-signals", "title": "Observability Signals and Alert Design", "description": "Operational signals, useful questions, and failure modes for service monitoring and incident diagnosis.", "tags": "devops,observability signals,reference,engineering", "view_count": 0, "created_at": 1791799200, "entry_count": 10, "summary": "Operational signals, useful questions, and failure modes for service monitoring and incident diagnosis. Each row includes a practical application and a failure to check before using it." }, { "id": 4, "slug": "site-reliability-practices", "title": "Site Reliability Practices", "description": "Key concepts from site reliability engineering.", "tags": "devops,sre,reliability", "view_count": 0, "created_at": 1783090350, "entry_count": 16, "summary": "The vocabulary of site reliability engineering: service-level indicators, objectives and agreements, error budgets, incident response and chaos engineering, with the metrics and routines around them such as MTTR, toil, postmortems, runbooks and the four golden signals." }, { "id": 5, "slug": "version-control-workflows", "title": "Version Control Workflows", "description": "Common branching and collaboration workflows.", "tags": "devops,git,workflow", "view_count": 0, "created_at": 1783090350, "entry_count": 9, "summary": "Branching and collaboration workflows for version control: centralized, feature branch, Gitflow, forking and trunk-based development, plus GitHub Flow, GitLab Flow, release branching and stacked changes. Each row says how work moves from a branch to release." }, { "id": 6, "slug": "virtualization-concepts", "title": "Virtualization Concepts", "description": "Key concepts in hardware virtualization and virtual machines.", "tags": "devops,virtualization,hypervisor,vm,cloud", "view_count": 0, "created_at": 1783090350, "entry_count": 13, "summary": "The concepts of virtualization: type 1 and type 2 hypervisors, virtual machines, paravirtualization, hardware-assisted virtualization and SR-IOV, plus live migration, snapshots, nested virtualization, ballooning, virtio drivers, device passthrough and thin provisioning." } ] }