Forum Discussion
Any Service Fabric Evangelists still out there?
We are heavily invested in Service Fabric and all our new microservices are built on top of SF. We use about 70% of the capabilities of SF.
I sometimes feel we are the only ones left, and the rest have either headed over to Kube or another orchestrator.
Please let me know if you still feel SF was the right choice for your product, and if not what have you replaced it with?
I sometimes feel we are the only ones left, and the rest have either headed over to Kube or another orchestrator.
Please let me know if you still feel SF was the right choice for your product, and if not what have you replaced it with?
3 Replies
We are still using SF. Our product is relying on Reliable Actors, so I think its the right choice. We didn't look into other orchestrator that has reliable actors (probably akka.net?).
I think the way Microsoft preach in microservices, they won't even mention SF. Maybe K8s is a better option?- It depends. If you are not using reliable collections you might be better of moving to K8S as there are more resources to be found. If you do use actors you can still move to K8S and use Orleans, a virtual actor framework (https://dotnet.github.io/orleans/) or DAPR actors (https://docs.dapr.io/developing-applications/building-blocks/actors/actors-overview/)
- We had started migrating away from SF around 2 years ago to k8s. Would never look back now. Part of the reason was containers coming in late to SF as k8s was starting to gain massive adoption. Now days the k8s ecosystem is very broad and has some other great practices (such as GitOps) being core to them and makes it much more compelling of a platform.
Dapr can also help in terms of migrating away from SF, I remember when it released I was definitely getting SF vibes and am actively using it in projects now.
