Architecting for uncertainty - part 5: DevOps defines how a fast-flow organization works

  • Published on Chris Richardson (microservices.io)
  • Curated on
Architecting for uncertainty - part 5: DevOps defines how a fast-flow organization works - Chris Richardson (microservices.io)
Image: Chris Richardson (microservices.io)

This is the fifth in a series of articles based on my talk Architecting for Fast Flow: Thriving Amid Uncertainty. In this series, I define the term fast flow and explain why it has become an essential software delivery capability. I discuss how fast flow emerges from a socio-technical architecture, which consists of a software architecture and its development organization. Finally, I describe how to design and evolve a socio-technical architecture in order to sustain fast flow.

The articles in the series are:

  1. Thriving in a VUCA world requires frequent deployment
  2. Fast flow defined
  3. GenAI as an amplifier
  4. Team topologies organizes for fast flow
  5. DevOps defines how a fast-flow organization works

Part 4 explained that fast flow is an emergent property of a socio-technical architecture, and described how Team Topologies structures the development organization for fast flow. In this article, I describe DevOps, which defines how a fast-flow organization gets work done. You will learn what DevOps is, and what it is not, which corrects a common misconception. You will also learn about the key technical practices of DevOps and their benefits.

Read more (This post is for paying subscribers only)

Need help with modernizing your architecture?

I help organizations modernize their architecture to enable fast flow and GenAI-powered software delivery. If you’re planning or struggling with a modernization effort, I can help.

Learn more about my modernization and architecture advisory work →