liveBook · Manning

DevOps

As explained in Microservices Patterns, Second Edition

A set of practices and cultural principles that integrates software development and operations to improve the flow and reliability of software delivery.

DevOps is an organization-wide way of working: a set of principles and practices for delivering software quickly and reliably, not a team name or job title. section 1.1.3

The three ways describe its foundational principles:

  • Move changes quickly from development into production. section 1.1.3
  • Return feedback quickly from production to development. section 1.1.3
  • Build a culture of continual experimentation and learning. section 1.1.3
Figure 1.3 Fast flow requires a combination of three elements: DevOps as the development process, an organization structured using the Team Topologies patterns, and an architecture that enables DevOps and Team Topologies.
SuccessTriangle Fast Flow Small

The fast-flow success triangle places DevOps alongside Team Topologies and architecture that enables both. section 1.1.3

DevOps is one part of fast flow, not a substitute for suitable organization and architecture. Before migrating a slow monolith to microservices, adopt DevOps and Team Topologies and establish an automated deployment pipeline; migrate only if these changes are insufficient and the architecture is the root cause. section 1.2 section 1.4.2

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the three ways and names reducing batch sizes, without enumerating the full set of principles.
Examples
Illustrates the success triangle linking DevOps, Team Topologies, and enabling architecture.
What you can do after
Apply DevOps organization-wide alongside suitable organization and architecture to pursue fast, reliable software delivery.
How it connects
Connects DevOps with Team Topologies, enabling architecture, and microservices as elements of fast software delivery.

Also explained in

Compare how 9 books explain DevOps →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.