Skip to content
dvnt.io

Resources · glossary

DevOps

A way of working in which building software and keeping it running are one responsibility, backed by automated deployment and monitoring. It is neither a job title nor a tool you can buy.

Also called
  • DevOps
  • DevOps culture
  • deployment automation
  • CI/CD
  1. 01

    What changes day to day

    Deployment stops being an event. Instead of an evening window once a quarter and a list of steps done by hand, a change goes live when it is ready, because the route to the server is handled by automation that does it the same way every time.

  2. 02

    What you actually pay for

    Deployment automation, a separate test environment and monitoring that alerts you before a customer does. It is work done once, with a running cost — not a full-time job.

  3. 03

    When it is overkill

    For a simple website changed once a quarter. A continuous deployment toolset then costs more attention than it saves, and the risk it protects against is small anyway.

  4. 04

    Signs it is missing

    Deployments at night, fear of releasing a fix and the question “who touched this last?” after every outage. These are not team problems but problems of a process that was never set up.

Related terms

  • Website maintenanceOngoing care of a live website: hosting, updates, backups, monitoring and small content changes. A cost you pay every month, whether or not anyone included it in the implementation quote.
  • BackupA copy of data and files kept separately from the live service, from which you can restore everything after a failure, a break-in or a simple mistake. A backup that has never been restored is an assumption, not protection.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.