Not sure why this comment was banned, it has valid points worth the conversation
—-
In my estimation, now would be a rather poor time to adopt SF.
1. It's poorly positioned against K8s. The "it can do containers" people are really not helping their case; SF's value proposition is clearly not in running arbitrary containers. Unless you're writing a new .NET app and will go all in on their SDK and replicated state model, it just doesn't make sense.
1a. It has no community. It has no presence outside of MS doc pages, the repo they threw over the wall, and the one external user that I'm aware of (who is already in this thread).
2. SF was operationally not-fun. I'm being nice. Though, neither is Kubernetes, most days.
3. SF is losing to Kubernetes, even internally, and even despite pressure from high-up-ish people.
4. The rumors about SFs fate would not seem to lend themselves toward adopting it for new projects.
—-
In my estimation, now would be a rather poor time to adopt SF.
1. It's poorly positioned against K8s. The "it can do containers" people are really not helping their case; SF's value proposition is clearly not in running arbitrary containers. Unless you're writing a new .NET app and will go all in on their SDK and replicated state model, it just doesn't make sense.
1a. It has no community. It has no presence outside of MS doc pages, the repo they threw over the wall, and the one external user that I'm aware of (who is already in this thread).
2. SF was operationally not-fun. I'm being nice. Though, neither is Kubernetes, most days.
3. SF is losing to Kubernetes, even internally, and even despite pressure from high-up-ish people.
4. The rumors about SFs fate would not seem to lend themselves toward adopting it for new projects.