> If there are 50 commits in every release, and a 2% chance of a given commit breaking something, then in expectation every monolith deploy gets rolled back. >

> If there are 50 commits in every release, and a 2% chance of a given commit breaking something, then in expectation every monolith deploy gets rolled back. > Microservices are one way out of that cycle. Is the implication that microservices lead to fewer bugs, or that microservices allow you to roll back one service instead of the monolith app as a whole? I would argue the former implication is a dubious claim, and the later doesn't make sense if other services depend on a given service running the latest version, which is often the case when implementing new features. If you are releasing bugs with every rollout that require a rollback, then perhaps a simpler solution is to do smaller releases with an improved testing/QA cycle.