摘录


By now it’s pretty well-known that a Microservices architecture has many advantages. These include low coupling, re-usability, business agility and distributed cloud ready applications. But at the same time it makes the architecture brittle because each user action results invokes multiple services. It replaces the in-memory calls of a monolithic architecture with remote calls across the network, which works well when all services are up and running. But when one or more services are unavailable or exhibiting high latency, it results in a cascading failure across the enterprise. Service client retry logic only makes things worse for the service, and can bring it down completely.

点评

NULL

原文

点击这里查看原文

其它

本帖内容由21QA云收藏工具自动生成,欢迎使用。

系统消息 若觉得内容不错,请点击左上角的"赞"图标,以优化网站的内容呈现。 另外,请及时验证注册邮箱,否则收不到21QA发出的红包。 官方Q群:250203055

asked 15 Jun '18, 16:09

%E8%B7%AF%E4%BA%BA%E7%94%B2's gravatar image

路人甲
131530584630

Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link: [text](http://url.com/ "title")
  • image: ![alt](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×754
×2

question asked: 15 Jun '18, 16:09

question was seen: 425 times

last updated: 15 Jun '18, 16:09

powered by O*S*Q*A

粤ICP备14040061号-1