Ask HN: In Microservices, How updates/upgrades of software tools are handled?

It may be the case that a given tool/framework doesn't offer enough value in return to the cost of maintaining it, particularly if it is making breaking changes that your team is forced to consume for some reason.

What happens if you cut the dependency and stop using the tool/framework? Is there an alternative that is much less costly to maintain?

> Which means they rapidly update to newer versions and/or change their design completely with breaking changes.

Do you have any examples? Most tools should provide a transition path that should ideally be painless but provide thorough documentation on how to upgrade when major changes do occur (which shouldn't be often). If you're seeing constant change you're probably using tools that aren't stable yet.

Is no one facing these issues ?