Thanks for the response, and for the question.

My point about the microservice stereotypes rely applies within the context of a team that has already set out to rebuild an entire vertical domain using microservices. In other words — per the example in the article — the “registration” team has already decided to rebuild the registration flow using microservices. That flow represents an entire vertical domain that will be effectively moved from the monolith to microservices.

So given that, what does the team do? They don’t want to just create random microservices willy nilly. Instead, they look to the organization’s catalog of stereotypes to help guide them in creating a well-organized set of services.