From the course: Azure Service Fabric for Developers

How does Azure Service Fabric work? - Azure Tutorial

From the course: Azure Service Fabric for Developers

Start my 1-month free trial

How does Azure Service Fabric work?

“

- [Instructor] Azure Service Fabric core functionality is based on two essential concepts: clusters and nodes. Generally speaking, nodes could be physical or virtual machines. Clusters are a group of connected nodes that form a highly available and highly reliable execution environment to run services and applications. Service Fabric supports any number of nodes in a cluster. To deploy a Service Fabric in a cluster, we install it in one of the nodes. Then Service Fabric is going to replicate itself to the remaining nodes in the cluster automatically. When Service Fabric is installed in all the nodes, it's going to ensure that they have connectivity between each other. In an Azure Service Fabric deployment, most of the time we have a load balancer that detects which nodes are healthy so that it could send requests to them and avoid unhealthy ones. To deploy an application we do it through the load balancer. The load balancer routes the request to one of the available nodes. Then Service Fabric will replicate the application to the remaining nodes. You don't have to do anything special to do this. Service Fabric is a scheduler. Finally, once the application is deployed, the load balancer will route the requests to one of the healthy and available nodes so that the application can respond. For this reason you can run Service Fabric applications in any operating system. Three main traits that stand out with this scenario: availability thanks to the redundant servers, reliability by creating multiple replicas of the data, and scalability by partitioning services. Partitioning is one of the main features of the reliable services programming model. Definitely, Service Fabric is an excellent option to host and run the most critical software solutions.

Contents