Service Fabric
Definition
Azure platform for building and managing microservices and container applications, simplifying deployment, scaling, and management.
Use Cases
- Microsoft: Running large-scale, always-on cloud services with microservices architecture — Microsoft built and operates parts of its own cloud services on Service Fabric, using clusters to host many microservices with automated health monitoring, rolling upgrades, and service discovery. (Improved service reliability and operational consistency by standardizing deployment, upgrades, and scaling across many microservices.)
- Azure DevOps (Microsoft): Hosting and scaling a multi-tenant developer platform with many backend services — Azure DevOps has been publicly described by Microsoft as using Service Fabric for microservice hosting, leveraging cluster management, application upgrades, and fault handling to run multiple services together. (Enabled frequent updates and resilient operations for a complex service composed of many independently deployable components.)
Provider Equivalents
- Azure: Azure Service Fabric
Frequently Asked Questions
- What's the difference between Azure Service Fabric and Kubernetes (AKS)?
- Both can run microservices and containers, but they differ in approach. Service Fabric is a platform with its own application model and runtime that supports both containerized workloads and Service Fabric services (including stateful services with built-in replication). AKS is managed Kubernetes, focused on running containers using Kubernetes APIs and ecosystem tools. Choose Service Fabric if you want its programming model and stateful service capabilities; choose AKS if you want Kubernetes standardization and broad portability.
- When should I use Service Fabric?
- Use Service Fabric when you need to run many microservices with strong lifecycle management (health monitoring, rolling upgrades, automatic failover) and you may benefit from Service Fabric features like stateful services or tight integration with the Service Fabric runtime. It’s commonly considered for advanced, long-running enterprise systems where you want a mature Microsoft-native microservices platform and are comfortable with its architecture and operational model.
- How much does Service Fabric cost?
- Service Fabric itself doesn’t have a separate license fee on Azure; you pay for the underlying infrastructure you run it on. Costs typically include the virtual machines in the cluster, storage, networking (including load balancers and bandwidth), and operational add-ons like monitoring. Pricing depends on cluster size, VM types, uptime requirements, and whether you run Windows or Linux nodes and containers.
Category: software
Difficulty: advanced
Related Terms
See Also