According to the Service Fabric docs (https://azure.microsoft.com/en-us/documentation/articles/service-fabric-reliable-actors-introduction/), an actor proxy is created this way:
ActorId actorId = ActorId.NewId();
IMyActor myActor = ActorProxy.Create<IMyActor>(actorId, new Uri("fabric:/MyApp/MyActorService"));
await myActor.DoWorkAsync();
Ok, this works and connects to my local cluster. But I cannot figure out how to create a proxy to a remote cluster? (I have a three-node cluster with the IPs 10.0.10.10, 10.0.11.10, 10.0.12.10.)
I also tried to use the ServicePartitionResolver, which is explained here: https://azure.microsoft.com/en-us/documentation/articles/service-fabric-reliable-services-communication/, but without success.
In order to add a new node type, modify your configuration to include the new node type in "NodeTypes" section under "Properties" and begin a configuration upgrade using Start-ServiceFabricClusterConfigurationUpgrade. Once the upgrade completes, you can add new nodes to your cluster with this node type.
Reverse proxy is an optional Azure Service Fabric service that helps microservices running in a Service Fabric cluster discover and communicate with other services that have http endpoints.
A single Service Fabric node type/scale set can not contain more than 100 nodes/VMs. To scale a cluster beyond 100 nodes, add additional node types.
ActorProxy and ServiceProxy today works best for connecting to actors and services within the cluster. You can expose a stateless service with -1 instance count that can accept the user requests and then use Actor and Service remoting to connect to the actor service within the cluster. In the future release we may offer out of the box application gateway that supports remoting.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With