Version and dependency is just a tool to achieve expected behavior for API. You still need to change versions centralized. The only difference is that monolith

Version and dependency is just a tool to achieve expected behavior for API. You still need to change versions centralized. The only difference is that monolith will not let you do that partially. Example there’s vulnerability in package, but only gateway exposed externally. Unless gateway still produced valid json/gRPC etc request it doesn’t really matter , you change a lib version without having impact on all other services that might be affected by library version change. It’s clear that article affected heavily by outdated Java way of building software. Where everything is injected by DI , AOP so even a small change in a core component is a big deal. No it’s not. Unless micro service is doing what expected and passes unit tests I don’t care. Even I change a language or db or network layer.