3 ms·

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

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.

GordonS 7y ago
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?
- shaklee3 7y ago
  Custom scheduler, a declarative API, the estimated of custom resources, many different filesystems natively supported, etc
  - GordonS 7y ago
    By "scheduler", do you mean as in "decides which nodes to run on"? You can build Service Fabric manifests with XML.
    - shaklee3 7y ago
      Yes, but from what I can tell in their documentation you cannot make the same level of decisions that you can with kubernetes.