concept volatility in category microservice

This is an excerpt from Manning's book Microservices in Action.
You can start by mapping these capabilities directly to microservices. Each service should reflect a capability that the business offers — this results in a good balance of size versus responsibility. You also should consider what would drive a microservice to change in the future — whether it truly has singleresponsibility. For example, you could argue that market execution is a subset of order management and therefore shouldn’t be a separate service. But the drivers for change in that area are the behavior and scope of the markets you’re supporting, whereas order management relates more closely to the types of product and the account being used to trade. These two areas don’t change together. By separating them, you isolate areas of volatility and maximize cohesiveness (figure 2.5).
By volatility — Services should encapsulate areas where change is likely to occur in the future.