Hacker News new | past | comments | ask | show | jobs | submit login

If 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.

No, 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.

As I remember it, it was a clear winner with no caveats. But my memory is shit, so there is that.

What features do you believe it's missing?

Custom scheduler, a declarative API, the estimated of custom resources, many different filesystems natively supported, etc

By "scheduler", do you mean as in "decides which nodes to run on"?

You can build Service Fabric manifests with XML.

Yes, but from what I can tell in their documentation you cannot make the same level of decisions that you can with kubernetes.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact