Use Case Description
Sometimes there is the use-case for a system that has the same basic requirements but needs some different logic in the core for different customers. The question is: Do the differences warrant a new microservice or do you put the logic in the same? Basically, the question is: A monolith or a zoo of microservices?
The answer depends on the requirements and both extremes are probably wrong.