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 articles in the series are:
1. Practice continuous delivery/deployment
2. Implement fast, automated deployment pipelines
4. Provide a great developer experience (DevEx)
5. Use a deliberative design process
6. Design independently deployable services
7. Design loosely coupled services
8. Design testable services
9. Develop observable services
10. Big/risky change => smaller/safer and (ideally easily) reversible changes - part 1 - incremental architecture modernization, part 2 - continuous deployment, part 3 - canary releases, part 4 - incrementally migrating users, part 5 - smaller user stories
11.Track and improve software metrics and KPIs
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.
