That’s the point. In the article, the scale is based not on the number of microservices but rather on the number of teams. There is no problem creating 100 microservices using the same stack if they are built by the same team or even by the same person. But the rules change when we force 100 teams to all use the same stack. Then, we should consider the overhead involved in making those 100 teams work with the same rules.

PS: Well, I’m not sure if 100 microservices built by the same person is also a good idea. Microservices, emerging from DDD, assume that each focuses on a single domain. Having 100 domains for one person could be overwhelming.