Availability of Service Fabric services
This article gives an overview of how Azure Service Fabric maintains the availability of a service.
Availability of Service Fabric stateless services
Service Fabric services can be either stateful or stateless. A stateless service is an application service that does not have a local state that needs to be highly available or reliable.
Creating a stateless service requires defining an
InstanceCount. The instance count defines the number of instances of the stateless service's application logic that should be running in the cluster. Increasing the number of instances is the recommended way of scaling out a stateless service.
When an instance of a stateless named-service fails, a new instance is created on an eligible node in the cluster. For example, a stateless service instance might fail on Node1 and be re-created on Node5.
Availability of Service Fabric stateful services
A stateful service has a state associated with it. In Service Fabric, a stateful service is modeled as a set of replicas. Each replica is a running instance of the code of the service. The replica also has a copy of the state for that service. Read and write operations are performed at one replica, called the Primary. Changes to state from write operations are replicated to the other replicas in the replica set, called Active Secondaries, and applied.
There can be only one Primary replica, but there can be multiple Active Secondary replicas. The number of active Secondary replicas is configurable, and a higher number of replicas can tolerate a greater number of concurrent software and hardware failures.
If the Primary replica goes down, Service Fabric makes one of the Active Secondary replicas the new Primary replica. This Active Secondary replica already has the updated version of the state, via replication, and it can continue processing further read/write operations. This process is known as reconfiguration and is described further in the Reconfiguration article.
The concept of a replica being either a Primary or Active Secondary, is known as the replica role. These replicas are described further in the Replicas and instances article.
For more information on Service Fabric concepts, see the following articles:
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.