Depends, the author suggests that one way to fix this is to extract the shared logic into a microservice of its own, but that may not be possible at all times.

Depends, the author suggests that one way to fix this is to extract the shared logic into a microservice of its own, but that may not be possible at all times. I also think that functionally, there's a very small difference between a library with a public API and a microservice with a public API - the only main advantage is that microservices can be written in any language, but that may not be important for many businesses. I think you should never "take it to heart", at least not in the meaning that you should follow advice slavically. It's just one more tradeoff you should be thinking of to avoid cargo culting.