微服务是你的最佳解决方案么？ #7463
Merged
微服务是你的最佳解决方案么？ #7463
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@lsvih 校对认领 |
|
@loststar 好的！ |
loststar
reviewed
Oct 6, 2020
|
@lsvih 校对认领 |
jackwener
reviewed
Oct 15, 2020
|
|
||
| Knowing the business domain inside out and the experience with the domain-driven design is crucial to identify the bounded context of each service. Since we allocate teams per each Microservice and allow them to work with minimal interference, getting the bounded context wrong would increase the communication overhead and inter-team dependencies, impacting the overall development speed. So for a project starting from scratch, selecting Microservices is a risky move. | ||
| 业务领域的全面了解和领域驱动设计服务的经验对于确定每个服务的有界上下文是至关重要的。我们为每个微服务分配团队，并使他们在干扰最小的情况下工作，但这会使每个团队误解边界上下文，增加通信开销和团队间的依赖性，从而影响整体开发速度。因此，对于一个从零开始的项目来说，选择微服务是一个有风险的举动。 |
There was a problem hiding this comment.
bounded context 在《领域驱动设计》的翻译中，更多的被翻译为：限界上下文。另外，为了读者能更加准确的理解，是否需要保留原有单词呢？
|
|
||
| Microservices isn’t a silver bullet or a superb architecture style that is for everyone. Since we need to deal with distributed systems, it could be an overkill for many. Therefore, it’s essential to assess whether the issues you are experiencing with the Monolith are solvable by Microservices. | ||
| 微服务不是精湛的架构风格，不是适合所有人的灵丹妙药。采用微服务我们需要处理分布式系统，这对许多人来说可能是极大的困难。因此，必须评估微服务是否可以解决您在单体应用中遇到的问题。 |
There was a problem hiding this comment.
『微服务不是精湛的架构风格，不是适合所有人的灵丹妙药』=>『微服务不是银弹，也不是适合所有人的高超架构风格』
|
|
||
| Finally, I want to finish this article by saying that be cautious if you decide to follow the Microservices approach from the beginning of a project. The journey seems to be more challenging than you think unless you have a solid case of following Microservices (For example, building an application for a specification or a given standard where you already know the bounded contexts, reducing overall risks). Or else, start with a Monolith. | ||
| 最后，在结束本文之前，我想说，如果您决定从项目开始就采用微服务，那么请务必谨慎。这个过程似乎比你想象的更具挑战性，除非你有一个坚实的理由来使用微服务 (例如，在你已经知道有限的上下文的情况下遵从规范或给定的标准构建一个应用程序，从而降低整体风险)。或者，你可以选择从一个单体应用开始构建。 |
There was a problem hiding this comment.
[有限的上下文]=>[限界上下文]
这个词是DDD中的术语
|
|
||
| If you grasp the message from Amazon and Netflix success stories, remember that they were successful with the Monolith as a business at first where they had the money and people with enough experience to do the transformation. These migrations might take months or years. But these businesses have the financials to back the digital transformation, knowing overall benefits at their scale. | ||
| 如果你从亚马逊和网飞的成功故事中得到启示，请记住，他们最初成功地将单体应用作为业务，从该业务获取足够的资金和人员来进行转型。这些迁移可能需要几个月或几年的时间。但是，这些企业有财务能力来支持数字化转型，因为它们知道自己的规模带来的总体利益。 |
There was a problem hiding this comment.
[因为它们知道自己的规模带来的总体利益]=>[知道自己的规模的总体利益]
没有因果关系
|
@jackwener 感谢校对！ @wangqinggang 回头您修改的时候劳请同步一下已经发好的文章哈~ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
译文翻译完成，resolve #7446