azure-service-fabric

How does one go about remoting into a node in a SF cluster? Since these are just VMs it feels like I should be able to RDP into them, even if that is something I would normally like to avoid. How would I go about remoting in? Adding a few Service Fabric-specific details to Vaclav's answer: The standard Service Fabric template defines a NAT that maps ports 3389 through 4500 to each VM's RDP port. To access the first VM in the scale set, use port 3389, the second VM, port 3390, etc. The host name is derived from the cluster's name, e.g. mycluster.eastus.cloudapp.azure.com (same address as SF

I have just started exploring Azure Service Fabric & I'm finding the concepts involved a little overwhelming Consider these 2 statements - " Service Fabric is agnostic to the underlying hosting provider. You can run it in Azure, you can run it on AWS, you can run it on 5 laptops - it doesn't matter. " " Azure Service Fabric for Windows Server ..can be used to..provision Service Fabric clusters in their own datacenters or other cloud providers, and run production workloads"... any Windows Server environment...there is no real lock-in to Azure as a cloud platform As per my understanding, 1) in

Service Bus Gateway is not starting. First of all I have tried completely uninstalling all Azure/Fabric/Service Bus type SDKs and installations. I have installed both Windows Azure Pack: Service Bus 1.1 and Windows Azure Pack: Security Update for Service Bus 1.1 (KB2972621) from scratch. After deleting all service bus related databases I start the Service Bus Configuration wizard and begin starting a new farm with custom settings. I leave everything default except adding my own certificates, and of course entering my password. After clicking go the the service bus configuration wizard

I see advantages of Kubernetes which include Rolling Deployments, Automatic Health check monitoring, and swinging a new server to action when an existing one fails. I also do understand that Kubernetes is not just for Docker. So, that brings a couple of questions! When Azure, and Service Fabric could provide all that I said (and beyond), why would I need Kubernetes? Would it make sense for one to use Kubernetes along with Service Fabric for large scale deployments on Azure? Let's look first at the similarities between Kubernetes and Service Fabric. They are both cloud-agnostic clustering,

I am new to Azure Service Fabric and the biggest questions I have are When should I use reliable actors? Give me practical examples please. When should I use reliable services? Give me practical examples please. Taken a look at the differences: State analogy : Actors work on a single instance of an object graph. Services usually have state for multiple callers. Scope : Actors can’t work alone, because of their size (more like objects). Life-cycle : Actors are only active when used, so more will fit on your available server resources Concurrency : Actors enforce single threaded access State :

Can anyone direct me to something that will explain when I should create an Azure Service Fabric application vs an Azure App Service application? I have an application I want to build but can not determine whether I should build it using the Azure Service Fabric or the Azure App Service. Microsoft has created the document with a comparison for Azure App Service, Virtual Machines, Service Fabric, and Cloud Services. Also, you might find helpful this decision tree. Unfortunately there isn't any official guidance about when to use what. They're two separate platforms, following different

After watching the BUILD conference videos for Azure Service Fabric, I'm left imagining how this might be a good fit for our current microservice-based architecture. There is one thing I'm not entirely sure how I would go about solving, however - the API gateway/proxy. Consider a less-than-trivial microservice architecture where you have N number of services running within the Azure Service Fabric exposing REST endpoints. In many situations, you want to package these fragmented API endpoints up into a single-entry API for consumers to use, to avoid having them connecting to the service fabric

I'm spending my evenings evaluating Azure Service Fabric as a replacement for our current WebApps/CloudServices stack, and feel a little bit unsure about how to decide when services/actors with state should be stateful actors, and when they should be stateless actors with externally persisted state (Azure SQL, Azure Storage and DocumentDB). I know this is a fairly new product (to the general public at least), so there's probably not a lot of best practices in regards to this yet, but I've read through most of the documentation made available by Microsoft without finding a definite answer for