Microservices rules #3: Apply Team Topologies
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. Let’s start by looking how team topologies fits into the fast flow success triangle.
