3 ms·

Microsoft already has a public kubernetes competitor that (comparatively) nobody uses: https://github.com/microsoft/service-fabric https://github.com/microsoft/

Microsoft already has a public kubernetes competitor that (comparatively) nobody uses: https://github.com/microsoft/service-fabric https://github.com/microsoft/service-fabric

daxfohl 7y ago
And the guy who created k8s originally is at Microsoft now, so I'd be interested to see how it all falls out if this prediction comes true.
- shaklee3 7y ago
  Brendan Burns has been leading the k8s/azure stuff for some time at Microsoft. I'm not sure internally how those two are competing, though.
  - daxfohl 7y ago
    He leads both AKS and service fabric. He just calls k8s the orchestrator for stateless services and SF the one for stateful ones.
shaklee3 7y ago
It looks like this project is dead at this point, with the last commit 6 months ago.
- daxfohl 7y ago
  No, they have a full hallway of people working on it and job openings on the careers site, and a good chunk of Azure core services use it with new services still being built on it. Supposedly it's pretty nice, since if you make sure to deploy your instances to different AZs, it takes care of synching all your in-memory data between instances and you can treat all of your data as in-memory data. You don't need a separate data layer, and supposedly everything is robust because you've got resiliency across AZs. At least that's what I've heard, though I've never used it and am curious about the actual resiliency and race handling.
  - shaklee3 7y ago
    Do you know why the oss project is stagnant? It would seem if they wanted it to gain traction they would use that repo as the main one. Someone else mentioned service fabric was for stateful services, but at this point stateful services in kubernetes are mature.
    - daxfohl 7y ago
      Nope, no idea.