microsoft/service-fabric

Service Fabric is a distributed systems platform for packaging, deploying, and managing stateless and stateful distributed applications and containers at...

Owned by Microsoft

View on GitHub ↗Jump to charts ↓Open shareable report →

microsoft/service-fabric has 3k+ stars and 400+ forks on GitHub, is written in C++, and was last pushed on Oct 12, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 22nd, 2026
Created on March 8th, 2018
Open Issues & Pull Requests: 849 (+0)
GitHub issues: Enabled
Number of forks: 402
Total Stargazers: 3,068 (+0)
Total Subscribers: 224 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 47.3 hours
Mean response time: 75.0 days
90th percentile: 82.3 days
Tracked items: 95

Maintainer activity

12 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "type-enhancement" is answered fastest, typically in about 11 hours, while "type-code-defect" waits about 4 days.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 76
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,412 days
Stale 30+ days: 74
Stale 90+ days: 69

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • type-code-defect (41)
  • type-enhancement (20)
  • status-last6months (8)
  • status-olderthan1year (3)
  • area-SDK (2)
  • type-question (2)
  • area-Communications-Networking (1)
  • area-Hosting-Containers (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Service Fabric is a distributed systems platform for packaging, deploying, and managing stateless and stateful distributed applications and containers at large scale.

Service Fabric addresses the challenge of building and operating enterprise-class, cloud-scale applications across heterogeneous environments. It provides a unified platform that handles both stateless and stateful workloads, running on Windows and Linux, across any cloud, datacenter, geographic regions, or local machines. The platform abstracts away the complexity of distributed systems management by offering built-in capabilities for deployment, orchestration, and lifecycle management of containerized and non-containerized applications.

Organizations building large-scale, mission-critical applications that require sophisticated state management and multi-region deployment should evaluate this platform. It suits enterprises already invested in Microsoft ecosystems or those needing to run applications across diverse infrastructure without vendor lock-in. The tool is particularly valuable for teams managing tier-1 applications that demand reliability and operational sophistication beyond what simpler container orchestrators provide.

The project is undergoing a transition to open development on GitHub while maintaining active internal development. The team publishes regular updates and roadmap items through official channels, and the repository includes comprehensive build infrastructure with documented requirements and timelines. Build times scale predictably with machine resources, ranging from approximately one hour on high-specification machines to several hours on smaller configurations, with clear documentation of disk and memory requirements for successful compilation.