liveBook · Manning

DevOps

As explained in Automating API Delivery

DevOps is a software delivery approach that integrates development and operations through lean principles, automation, feedback, and continuous learning.

As an organization adds API teams, friction between developers and platform or operations teams can force a tradeoff between delivery speed and quality. DevOps addresses that friction by applying lean principles across development and operations to deliver customer value quickly and reliably. section 1.2

Three principles guide the work:

  • Move valuable work quickly through the technology value stream. section 1.2
  • Send feedback back through the value stream so problems are detected and fixed quickly. section 1.2
  • Foster continuous learning, sharing, and experimentation in a high-trust environment. section 1.2

Version control makes code and configuration changes reviewable and recoverable. Continuous integration repeatedly integrates tested code into a shared branch and packages deployable artifacts; continuous delivery automates deployment to test or production environments. Together, these practices support shorter lead times without accepting a higher change failure rate. section 1.2

How Automating API Delivery covers it

How deep it goes
Defines three governing principles and describes version control and CI/CD practices, without specifying commands or pipeline configuration.
Examples
Uses a growing organization's API workflow to illustrate friction between development and platform or operations teams.
What you can do after
Evaluate/understand how DevOps practices can reduce API delivery lead times while limiting change failures.
How it connects
Connects lean principles, feedback, continuous learning, version control, and CI/CD to API delivery.

Also explained in

Compare how 7 books explain DevOps →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.