service-discovery

问题 I am trying to make 2 services communicate over service discovery endpoint in AWS ECS service. Example: Service1: runs the Task Definition to run nginx and phpfpm Service2: runs the Task Definition to run redis Now, I need to make service1 container communicate to service2 container As per the documentations and resource found on internet. This is what I have done and not able to achieve the need. We need to turn on service discovery ( Done ) Set proper service name and namespace which will

问题 I am trying to make 2 services communicate over service discovery endpoint in AWS ECS service. Example: Service1: runs the Task Definition to run nginx and phpfpm Service2: runs the Task Definition to run redis Now, I need to make service1 container communicate to service2 container As per the documentations and resource found on internet. This is what I have done and not able to achieve the need. We need to turn on service discovery ( Done ) Set proper service name and namespace which will

问题 I'm trying to add ad-hoc discovery to a simple WCF service-client setup (currently implemented by self hosting in a console app). Debugging using VS2010 on windows 7, and doing whatever I can find in online tutorial, but still - the discovery client simply finds nothing. Needless to say if I open a client to the correct service endpoint I can access the service from the client. service code: using (var selfHost = new ServiceHost(typeof(Renderer))) { try { selfHost.Open(); ... selfHost.Close()

问题 I'm trying to add ad-hoc discovery to a simple WCF service-client setup (currently implemented by self hosting in a console app). Debugging using VS2010 on windows 7, and doing whatever I can find in online tutorial, but still - the discovery client simply finds nothing. Needless to say if I open a client to the correct service endpoint I can access the service from the client. service code: using (var selfHost = new ServiceHost(typeof(Renderer))) { try { selfHost.Open(); ... selfHost.Close()

问题 I'm trying to add ad-hoc discovery to a simple WCF service-client setup (currently implemented by self hosting in a console app). Debugging using VS2010 on windows 7, and doing whatever I can find in online tutorial, but still - the discovery client simply finds nothing. Needless to say if I open a client to the correct service endpoint I can access the service from the client. service code: using (var selfHost = new ServiceHost(typeof(Renderer))) { try { selfHost.Open(); ... selfHost.Close()

问题 I m studying Microservices architecture and I m actually wondering something. I m quite okay with the fact of using (back) service discovery to make request able on REST based microservices. I need to know where's the service (or at least the front of the server cluster) to make requests. So it make sense to be able to discover an ip:port in that case. But I was wondering what could be the aim of using service registry / discovery when dealing with AMQP (based only, without HTTP possible

问题 I have a service fabric cluster hosting legacy WCF services. Each of the WCF services is allocated a port number and uses the net.tcp protocol. I wonder what is the best way for service discovery and auto-scaling? I tried service fabric's DNS service and let service fabric assigns the port number for each service, however, the client won't know about the dynamic port number. The DNS service can only resolve the ip-address based on service DNS name. Since each service is on a specific port, I

问题 I have a kubernetes cluster with serviceA on namespaceA and serviceB on namespaceB. I want, from serviceA, use kubernetes service discovery to programmatically list serviceB. I am planning to use spring cloud kubernetes ( @EnableDiscoveryClient ). However, there is a company wide policy to block the use of the configuration below that should have solved the problem: spring.cloud.kubernetes.discovery.all-namespaces=true Is there any way to circumvent the problem? Maybe assign serviceB to two

问题 I have a scenario where I have to deploy multiple micro-services on AWS ECS. I want to make services able to communicate with each other via APIs developed in each micro-service. I want to deploy the front-end on AWS ECS as well that can be accessed publicly and can also communicate with other micro-services deployed on AWS ECS. How can I achieve this? Can I use AWS ECS service discovery by having all services in a private subnet to enable communication between each of them? Can I use Elastic

问题 I am developing an Android Application that employs WiFi (Direct) for service discovery and P2P peer discovery/connection. My development enviromment is as follows:- Android Studio 3.0 Beta 4 Build #AI-171.4304935, built on August 29, 2017 JRE: 1.8.0_152-release-915-b01 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Mac OS X 10.11.6 My Gradle build:- apply plugin: 'com.android.application' apply plugin: 'realm-android' android { compileSdkVersion 26 buildToolsVersion "26.0.1"