azure-service-fabric

My thinking is that people use Docker to be sure that local environment is the same as production and that I they can stop thinking about where are their apps running physically and balancing mechanisms should just allocate apps in best places for that moment. I'm 100% web based and I'm going to move to cloud together with our databases, and what cannot be moved will be seamlessly bridged so the corporate stuff and the cloud will become one subnetwork. And so I'm wondering, maybe Service Fabric already does the same thing that Docker does plus it gives as address translation service (fabric://

I need to implement pipeline if Service Fabric's Reliable Services, and I need some guidelines about what of these approaches is preferable from the viewpoint of reliability simplicity and simple good design: I have been investigating this topic a lot as well (to be applied to my work for NServiceBus and MessageHandler ) and would like to provide my thoughts on the matter. However I haven't determined what the best model is yet. If you disregard the practical implementation with ServiceFabric I would categorize the proposed approach in the following order when it comes to reliability: C) The

Is it possible to use signalR with Service Fabric provided by Microsoft? I'm trying to connect an UWP app and an angularJS app to my stateless reliable service hosted in an Azure Cluster through signalR/websocket connection. But both are not able to open such a connection. On my local machine everything works fine. Is there anything special to consider of using signalR/websockets with Service Fabric? Is there any example? Kevin Daniel Setiono You need to configure the load balancer to the client ip. Then the user will always get to the same node and other users to other nodes. The user to node

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

I have a Visual Studios solution containing the following: Service Fabric project Stateless Service Project The stateless service project uses configuration-based dependency injection, meaning the dependencies are loosly coupled with the project itself and not actual VS "project/compilation dependencies". I would like to continue to use Visual Studios, but when I deploy this project it doesn't know about the assembly dependencies (as these are only defined in DI configuration) and therefore it doesn't package up the necessary files and throws exceptions trying to perform dependency injection.

We are developing a .Net Core service that shall be hosted in Azure Service Fabric. This SF Service needs to interact with 10,000 devices registered in Azure IoT Hub via it's AMQP 1.0 SSL TLS endpoints. Each IoT Hub devices has it's own security tokens and connection string provided by the IoT Hub service. For our scenario we need to listen to all cloud-to-devices messages coming from the 10,000 IoT Hub device instances and "route" these to a central Service Bus topic to which the actual "gateways" in the field listen to. So basically we want to forward messages from 10,000 Service Bus Queues