Saltar al contenido ForoHackers

DevOps: start here

DevOps
#687 · Ophuscado · · Denunciar

DevOps is the practice of making the people who build software and the people who run it one team with shared goals. The aim is to ship small changes often, safely and with fast feedback, by automating the path from a commit to production and by owning what you release.

Key concepts

  • Shared ownership: the team that writes a service also deploys it, watches it and is called when it breaks.
  • Automation of the path: build, test, release and rollback are scripts, not rituals done by hand.
  • Small batches: many tiny changes are easier to review, test and undo than one huge release.
  • Infrastructure as code: servers and networks are described in files kept in version control.
  • Feedback loops: metrics, logs and incident reviews flow back into the next change.

Vocabulary

  • Pipeline: the automated sequence of steps a change passes through on its way to production.
  • Lead time: how long a commit takes to reach users; deployment frequency is how often that happens.
  • Rollback: returning to the previous known-good version.
  • Blameless review: studying a failure for its causes in the system, not for a culprit.

What to study, in order

  1. Git and the command line, until branching and scripting feel ordinary.
  2. Run a small web service on a Linux machine by hand, and write down every step you took.
  3. Turn those steps into a script, then into a pipeline that tests and deploys on each push.
  4. Package the service in a container and describe its environment as code.
  5. Add health checks, logs and one alert; break the service on purpose and practise the rollback.

Related tags

#ci-cd #sre #containers #version-control

Inicia sesión o únete para responder.