I'm now a Team Topologies Advocate! 🎉

team topologies   architecting   architecture  

---

---

I’m very excited to announce that I’m now a Team Topologies Advocate! I’ve been a big fan of Team Topologies since it was published and so was quite honored when Matthew Skelton asked me to become an advocate.

The concepts that Team Topologies describes have played a major role in my thinking and work for many years. The intersection of Team Topologies and software architecture is very exciting and fruitful. Here is a brief history.

Microservices Patterns: the Success Triangle

For example, in my 2018 book Microservices Patterns I described the success triangle. It shows the relationship between the three ingredients necessary for the rapid, frequent and reliable delivery of software (today known as fast flow):

As I wrote in the book:

For a large, complex application, the microservice architecture is usually the best choice. But in addition to having the right architecture, successful software development requires you to also have organization and development and delivery processes.

The success triangle’s organization structure is a loosely coupled network of small product teams.

The Success Triangle and Team Topologies

When Team Topologies was published, it provided a robust set of patterns and concepts to achieve this organization structure.

Here’s an updated version of the success triangle:

Please read the post to learn more about the books for high-performance software delivery.

The Success Triangle and fast flow

I recently reinterpreted the success triangle from the perspective of fast flow.

Here’s the latest version:

>

New workshop: Architecting for fast, sustainable flow

I’ve created a new workshop that describes how to architect for fast, sustainable flow. It covers both the monolithic and microservice architectures. Learn more about Architecting for fast, sustainable flow - enabling DevOps and Team Topologies thru architecture.

The intersection of Team Topologies and software architecture

Going forward, I’m looking forward to collaborating with the Team Topologies community and continuing to evolve my thinking around the intersection of Team Topologies and software architecture.

Need help with modernizing your architecture?

I help organizations modernize safely and avoid creating a modern legacy system — a new architecture with the same old problems. If you’re planning or struggling with a modernization effort, I can help.

Learn more about my modernization and architecture advisory work →