While defining this problem, we mentioned the common library lying in a different microservice, which will bound us to use any one particular language. To avoid this, we should adopt another bad habit, which is code redundancy. To make microservice completely isolated from each other, code replication is used. This will solve the issue of dependency and will give the freedom of language choice also. This is a tradeoff, but it is not the best solution. After some time, when microservice architecture evolves more, then we might have more practices in action, and that will give us a better idea. Also, whenever we change any dependency, we should not break the backward compatibility until all the services come to a new version. When all the services come to the latest version, then we can remove the old version.