No right answer to this question under all circumstances.

▪ Bounded Context can create more than one Microservice.

▪ Decision to be made based on the microservice's need for scalability and independence.

▪ Since Bounded Context defines the boundaries of the domain, a Microservice determines the technical and organizational boundaries.

▪ Similar to Microservices, Bounded Contexts are autonomous and responsible by certain domain capability.

▪ Context Mapping and the Bounded Context pattern are good approaches for identifying microservices.

https://medium.com/@vladikk.com/bounded-contexts-are-not-microservices-ead44b8d6e35

We can say that there is no right answer to this question under all circumstances.

A Microservice can represent a Bounded Context or part of it. In other words, a Bounded Context can create more than one Microservice. This is entirely a decision to be made based on the microservice’s need for scalability and independence.

While a Bounded Context defines the boundaries of the domain, a Microservice determines the technical and organizational boundaries as the same way of BC domains.

But nevertheless, this approach can be use when defining microservices from bounded contexts. Because this is similar to the definition of a microservice: it’s autonomous and responsible by certain domain capability.

So this is why Context Mapping and the Bounded Context pattern are good approaches for identifying microservices. We will also follow this pattern when decomposing microservices.