《microservice design》

一、原文：

In a large monolithic application, even if just one line of code is modified, the entire application needs to be redeployed to publish that change. This deployment method has significant impact and risk, so relevant personnel are hesitant to deploy easily. Therefore, in practice, deployment frequency is often low. This means that between two releases, we have made many feature enhancements to the software, but only release these changes to the production environment at the last minute. In this case, another problem arises: the greater the difference between releases, the greater the likelihood of errors!

In a microservices architecture, each service can be deployed independently, allowing for faster deployment of specific parts of the code. If a problem occurs, it only affects one service and can be quickly rolled back. This also means that customers can use our new features faster. Organizations like Amazon and Netflix adopt this architecture mainly based on the above considerations. This architecture effectively solves various obstacles in software release.

二、翻译

在庞大的单块应用程序中，即使仅仅修改了一行代码，也需要重新部署整个应用程序才能发布这个变更。这种部署方法带来了巨大的影响和风险，因此相关人员不敢轻易进行部署。因此，在实践中，部署频率往往很低。这意味着在两次发布之间，我们对软件进行了许多功能增强，但直到最后一刻才将这些变更一次性发布到生产环境中。这种情况下，另一个问题就出现了：发布之间的差异越大，出错的可能性就越大！ 微服务架构中的各个服务可以独立部署，这样可以更快地部署特定部分的代码。如果发生问题，只会影响一个服务，并且可以快速回滚，这也意味着客户可以更快地使用我们开发的新功能。像Amazon和Netflix这样的组织采用这种架构主要是基于上述考虑。这种架构有效地解决了软件发布过程中的各种障碍。