Microservices rules #3: Apply Team Topologies

team topologies success triangle microservices rules

This is another article in the series about microservices rules: what good looks like, which are a set of principles and practices for using microservices effectively. The other articles about microservices rules are:

Microservices rules #1 - continuous delivery/deployment
Microservices rules #2: Implement fast, automated deployment pipelines
Microservices rules #5: Deliberative design
Microservices rules #10: part 1 - incremental architecture modernization
Microservices rules #10: part 2 - continuous deployment
Microservices rules #10: part 3 - canary releases
Microservices rules #10: part 4 - incrementally migrating users

Microservices rules #3 is Apply team topologies. In this article, I provide a brief overview of team topologies. You will learn why you should adopt team topologies when using microservices. I explain how microservices enable team topologies. You will also learn about the different kinds of platforms that are needed in a microservice architecture.

team topologies success triangle microservices rules

Follow @crichardson

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.

ASK CHRIS

Got a question about microservices?

Fill in this form. If I can, I'll write a blog post that answers your question.

NEED HELP?

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

Learn more about my consulting engagements, and training workshops.

PREMIUM CONTENT

Premium content and office hours is now available for paid subscribers at premium.microservices.io.

MICROSERVICES WORKSHOPS

Chris teaches comprehensive workshops for architects and developers that will enable your organization use microservices effectively.

Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.

Learn more

Remote consulting session

Got a specific microservice architecture-related question? For example:

Wondering whether your organization should adopt microservices?
Want to know how to migrate your monolith to microservices?
Facing a tricky microservice architecture design problem?

Consider signing up for a two hour, highly focussed, consulting session.

ASSESS your architecture

Assess your application's microservice architecture and identify what needs to be improved. Engage Chris to conduct an architect review.

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 NTOQTWTO to sign up for $95 (valid until February 9th, 2025). 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

For Email Marketing you can trust.

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

Microservice Architecture