blocks|key|1861257|text|如果微服务确实需要相互交谈，通常它的via+REST+(因为您有noticed.However微服务纯粹主义者)可能反对这种依赖关系。除此之外，服务发现是通过将可用的端点发布到服务注册中心-+蚀刻+(在CloudFoundry的情况下)来实现的。一旦注册了端点，给定服务的各种实例就可以使用POST操作将自己注册到注册表。客户端只需要知道已发布的端点，而不需要了解单个服务实例的终结点。这是自我注册。客户机将要么与诸如ELB之类的负载平衡器通信，后者查找服务注册中心，要么客户端应该知道服务注册中心。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1861258|对于(2)，如果正在设计这样一组耦合的服务，指出一些迫在眉睫的问题，例如编排和同步，那么微服务之间就不应该存在像微服务定义那样的硬依赖关系。如果出现这种依赖关系，您将依赖于服务注册中心、健康检查和中断电路。|1861259|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/coreos/etcd|1|http://microservices.io/patterns/self-registration.html^0|2O|2|0|5F|5|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

If micro-services do need to talk to each other, generally its via REST as you have noticed.However microservice purists may be against such dependencies. That apart, service discovery is enabled by publishing available endpoints on to a service registry - <a href="https://github.com/coreos/etcd" rel="nofollow">etcd</a> in case of CloudFoundry. Once endpoint is registered, various instances of a given service can register themselves to the registry using a POST operation. Client will need to know only about the published end point and not the individual service instance's end point. This is <a href="http://microservices.io/patterns/self-registration.html" rel="nofollow">self-registration.</a> Client will either communicate to a load balancer such as ELB, which looks up service registry or client should be aware of the service registry.

For (2), there should not be such a hard dependency between micro-services as per micro-service definition, if one is designing such a coupled set of services that indicates some imminent issues such as orchestrating and synchronizing. If such dependencies do emerge, you will have rely on service registries, health-checks and circuit-breakers for fall-back.

blocks|key|1861290|text|ref-app“应用程序”由几个“应用程序”和“服务”组成。应用程序通过manifest.yml中的一个条目绑定到服务。因此，它通过这个绑定获取服务端点和其他重要的配置信息。当应用程序绑定到服务时，'cf‘命令返回所需的信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1861291|属性文件中可能仍然有一些服务端点信息，但是随着时间的推移，这些信息将被重构。|1861292|ref-app应用程序的各个应用程序被放置在单独的微服务中，因为它们被用作其他应用程序的组件。因此，采用微观服务方法。如果应用程序之间存在启动依赖关系，则将应用程序推入云端的CI/CD管道将需要管理这些依赖关系。ref-app中的依赖关系就是显而易见的依赖关系。|1861293|的确，微服务的耦合并不在设计中。有一些明显的原因可能会发生。语言和功能。如果您有一个用Java编写的“后端”微服务，而“前端”UI微服务是用NodeJS上的Javascript编写的，那么这些服务将作为两个单独的应用程序推送。从理论上讲，如果没有后端，UI就不能很好地工作，但是有一个计划要用一些固定的JSON来实现。但还是有一些逻辑耦合。|1861294|您从微服务中获得的好处是，它们可能需要不同的扩展，而云铸造厂使用“cf+scale”命令非常容易。它们可能被多个其他微服务使用，从而产生新的规模需求。因此，考虑什么需要扩展，以及功能的发布周期，有助于决定什么是微服务。|1861295|例如，关于排序，您的应用程序可能需要Google，因此可以说应该先启动它，然后再启动您的应用程序。但实际上，您的应用程序应该考虑到映射api可能会下降。您的目标应该是当依赖的微服务不可用时，您的应用程序表现良好。|1861296|“应用程序”的“应用程序”知道每个应用程序的名称和云给它的URL。实际上，在不同的云和空间中运行的参考应用程序有很多副本。它们是以诸如Dev、QA或Integration之类的东西作为前缀的。我们是否可以让Dev前端与QA后端微服务进行对话，当然，这只是一个URL。|1861297|除了前面提到的etcd+(我还没有尝试过)之外，您还可以创建CUPS服务“definition”。这也是一组键/值对。您可以将其绑定到空间(dev/qa/工作台/prod)，并通过清单绑定它们。这样你才能从环境中得到道具。|1861298|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

The ref-app 'application' consists of several 'apps' and Predix 'services'. An app is bound to the service via an entry in the manifest.yml. Thus, it gets the service endpoint and other important configuration information via this binding. When an app is bound to a service, the 'cf env ' command returns the needed info.

There might still be some Service endpoint info in a property file, but that's something that will be refactored out over time.

The individual apps of the ref-app application are put in separate microservices, since they get used as components of other applications. Hence, the microservices approach. If there were startup dependencies across apps, the CI/CD pipeline that pushes the apps to the cloud would need to manage these dependencies. The dependencies in ref-app are simply the obvious ones, read-on.

While it's true that coupling of microservices is not in the design. There are some obvious reasons this might happen. Language and function. If you have a "back-end" microservice written in Java used by a "front-end" UI microservice written in Javascript on NodeJS then these are pushed as two separate apps. Theoretically the UI won't work too well without the back-end, but there is a plan to actually make that happen with some canned JSON. Still there is some logical coupling there.

The nice things you get from microservices is that they might need to scale differently and cloud foundry makes that quite easy with the 'cf scale' command. They might be used by multiple other microservices, hence creating new scale requirements. So, thinking about what needs to scale and also the release cycle of the functionality helps in deciding what comprises a microservice.

As for ordering, for example, the Google Maps api might be required by your application so it could be said that it should be launched first and your application second. But in reality, your application should take in to account that the maps api might be down. Your goal should be that your app behaves well when a dependent microservice is not available.

The 'apps' of the 'application' know about each due to their name and the URL that the cloud gives it. There are actually many copies of the reference app running in various clouds and spaces. They are prefaced with things like Dev or QA or Integration, etc. Could we get the Dev front end talking to the QA back-end microservice, sure, it's just a URL. 

In addition to the aforementioned, etcd (which I haven't tried yet), you can also create a CUPS service 'definition'. This is also a set of key/value pairs. Which you can tie to the Space (dev/qa/stage/prod) and bind them via the manifest. This way you get the props from the environment.

I'm a newbie in Cloud Foundry. In following the reference application provided by Predix (<a href="https://www.predix.io/resources/tutorials/tutorial-details.html?tutorial_id=1473&amp;tag=1610&amp;journey=Connect%20devices%20using%20the%20Reference%20App&amp;resources=1592,1473,1600" rel="nofollow">https://www.predix.io/resources/tutorials/tutorial-details.html?tutorial_id=1473&amp;tag=1610&amp;journey=Connect%20devices%20using%20the%20Reference%20App&amp;resources=1592,1473,1600</a>), the application consisted of several modules and each module is implemented as micro service.

My question is, how do these micro services talk to each other? I understand they must be using some sort of REST calls but the problem is:

<ol>
<li>service registry: Say I have services A, B, C. How do these components 'discover' the REST URLs of other components? As the component URL is only known after the service is pushed to cloud foundry.</li>
<li>How does cloud foundry controls the components dependency during service startup and service shutdown? Say A cannot start until B is started. B needs to be shutdown if A is shutdown.</li>
</ol>

How do micro services in Cloud Foundry communicate?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我是云铸造公司的新手。在遵循提供的参考应用程序的过程中，该应用程序由多个模块组成，每个模块都被实现为微服务。我的问题是，这些微型服务是如何相互交流的？我知道他们一定在使用某种REST调用，但问题是：服务注册中心:假设我有服务A、B、C，这些组件是如何“发现”其他组件的其他URL的？作为组件，只有在服务被推到云铸造厂之后...

问云铸造中的微服务是如何进行通信的？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问云铸造中的微服务是如何进行通信的？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问云铸造中的微服务是如何进行通信的？
EN