The success triangle reinterpreted: it's all about fast flow

architecting   success triangle   fast flow   team topologies   architecture   devops  

In a previous article, I described how the success triangle has evolved over the years since I first introduced it in my 2018 book Microservices patterns. The core idea of the success triangle is that the rapid, frequent, reliable and sustainable delivery of software requires three elements:

  • DevOps (as defined by the DevOps handbook)
  • Team Topologies
  • Architecture

In this article, I reinterpret the success triangle from the perspective of fast flow.

About fast flow

‘Fast flow’ has been on my mind recently after I listened to my Susanne Kaiser’s excellent ExploreDDD talk Optimizing for a fast flow of value with adaptive, socio-technical systems. To quote the abstract:

This talk explores the synergy of Wardley Mapping, Domain-Driven Design (DDD), and Team Topologies as a holistic toolkit for building adaptive, socio-technical systems optimized for a fast, sustainable flow of value and feedback.

The key idea of fast flow is that an organization’s structure, culture and work practices along with its application architecture should be such that it delivers a continuous stream of valuable changes to its customers. The underlying metaphor is of a river flowing fast and smoothly, with no blockages or bottlenecks.

The fast flow success triangle

The primary objective of two of the success triangle’s elements - DevOps and Team Topologies - is to facilitate fast flow. The first way of DevOps is about the fast flow of changes from dev to ops. Fast flow is also a goal of the Team Topologies. The book’s subtitle is ‘Organizing business and technology teams for fast flow’. Moreover, as I previously described, the goal of the success triangle’s architecture element is to enable DevOps and Team Topologies. It makes sense, therefore, to view the goal of the success triangle to be the fast, sustainable flow of changes.

Here’s the success triangle from the perspective of fast flow.

A socio-technical architecture for fast flow

The three elements of the success triangle comprise a socio-technical system (or, as recently described in the InfoQ Software Architecture and Design Trends Report - April 2024, a Socio-technical architecture) for fast flow.

Need help with accelerating software delivery?

I’m available to help your organization improve agility and competitiveness through better software architecture: training workshops, architecture reviews, etc.

Learn more about how I can help

Learn more about my new public workshop Architecting for fast, sustainable flow - enabling DevOps and Team Topologies thru architecture.


architecting   success triangle   fast flow   team topologies   architecture   devops  


Copyright © 2024 Chris Richardson • All rights reserved • Supported by Kong.

About Microservices.io

Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.

Upcoming public workshops: Microservices and architecting for fast flow

In-person: Berlin and Milan

DevOps and Team topologies are vital for delivering the fast flow of changes that modern businesses need.

But they are insufficient. You also need an application architecture that supports fast, sustainable flow.

Learn more and register for one of my upcoming public workshops in November.

NEED HELP?

I help organizations improve agility and competitiveness through better software architecture.

Learn more about my consulting engagements, and training workshops.

LEARN about microservices

Chris offers numerous other resources for learning the microservice architecture.

Get the book: Microservices Patterns

Read Chris Richardson's book:

Example microservices applications

Want to see an example? Check out Chris Richardson's example applications. See code

Virtual bootcamp: Distributed data patterns in a microservice architecture

My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!

It covers the key distributed data management patterns including Saga, API Composition, and CQRS.

It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.

The regular price is $395/person but use coupon CCMHVSFB to sign up for $95 (valid until November 8th, 2024). There are deeper discounts for buying multiple seats.

Learn more

Learn how to create a service template and microservice chassis

Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.

Signup for the newsletter


BUILD microservices

Ready to start using the microservice architecture?

Consulting services

Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,


The Eventuate platform

Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.

Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.


Join the microservices google group