5 ms·
Which orchestrator are you referring to? System Center in no way competes with kubernetes since it's lacking 90% of the features. Maybe I'm bad at googling, but
by shaklee3 7y ago
Which orchestrator are you referring to? System Center in no way competes with kubernetes since it's lacking 90% of the features. Maybe I'm bad at googling, but I can't find what you're referring to.
Edit: I see the one you're referring to in that link, but again, it's not at all a comparison with kubernetes. It's easy at face value to say this one is better, but it's missing the point of kubernetes, which is extensibility, following standards, etc.
- sciurus 7y agoThey linked it. Service Fabric. > Service Fabric is a distributed systems platform for packaging, deploying, and managing stateless and stateful distributed applications and containers at large scale. https://github.com/Microsoft/service-fabric https://github.com/Microsoft/service-fabric
- oldmanhorton 7y agoRE your edit, Service Fabric came out well before any standards existed.
- cc81 7y ago>following standards What standards?
- shaklee3 7y agoCNI, CSI, OCI
- GordonS 7y agoIf you Google it you'll find several comparisons to k8s and others. I looked into this a while back, and Service Fabric was a clear winner over k8s, and resource use was a fraction of k8s too. But, I felt it needed to gain community traction before I could commit to using it - knowing my luck, I'd build something and Microsoft would abandon it because k8s... Kind of a chicken and egg problem, which is a shame really.
- shaklee3 7y agoNo, it was a clear winner for your use case. It's missing a significant amount of features from k8s, though, and if you don't need those, then great. But don't pretend they're comparable. I think it's more fair to say the suit different use cases (an MS person on HN explicitly said this last year), rather than competing.