6 ms·

It's worth noting that while Service Fabric as a technology does power a lot of offerings at Microsoft (as noted in the article), strategically it has been supe

by wenc 8y ago

It's worth noting that while Service Fabric as a technology does power a lot of offerings at Microsoft (as noted in the article), strategically it has been superseded somewhat by Azure Kubernetes Service (AKS). Most new development should really be on AKS. Even Azure Container Instances (ACI), a recently GA'ed Azure service, runs Kubernetes underneath. Edit: As noted in the comments, SF is on Github. The following paragraph is incorrect and I retract what I said; leaving this here for context. "Also, by going the K8S route, you potentially avoid being locked into a proprietary offering -- SF is only available from one vendor, whereas K8S is available almost anywhere."

manigandham 8y ago
Service Fabric is different from Kubernetes. It's not a container orchestration platform but a full-stack distributed state and processing system with components that can serve as the foundation for building something like Kubernetes itself. The naming is confusing and there is a Service Mesh offering from Azure that lets you run your own applications easily if they're using the Service Fabric framework already, but SF can run containerized code in any language, and it has bindings for C# and Java (for now) if you want to use the primitives directly. SF is also now open-source and you can run it all yourself in whatever environment you want: https://github.com/Microsoft/service-fabric https://github.com/Microsoft/service-fabric
- dewiz 8y ago
  SF has been opensourced very late though [1], to get some attention and trying to survive. Legitimate but very different from being an open source project. The cross-platform support is very weak [2][3], far from K8S, Mesos and Swarm developer friendliness. [1] https://blogs.msdn.microsoft.com/azureservicefabric/2018/03/14/service-fabric-is-going-open-source https://blogs.msdn.microsoft.com/azureservicefabric/2018/03/... [2] https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started-mac https://docs.microsoft.com/en-us/azure/service-fabric/servic... [3] https://social.msdn.microsoft.com/Forums/en-US/b5045fe1-51a2-4c58-ae90-53c145d3ef59/using-mac-with-azure-service-fabric https://social.msdn.microsoft.com/Forums/en-US/b5045fe1-51a2...
  - manigandham 8y ago
    Trying to survive? It already runs all of Microsoft's cloud services and does just fine. Open-sourcing was more of a good-will move so that the community can also use it, similar to how Apple released FoundationDB. The links you point to are about developing with SF, which doesn't natively run on Mac OSX. It can run on Linux but has fewer features for now, but this is being worked on. It's not the same as K8S/Mesos/Swarm though so if container orchestration is all you need then you shouldn't use SF.
  - polskibus 8y ago
    I don't think it's buildable on Windows yet. It's been like this for a couple of months now, not sure if MS is really trying to get others involved.
    - dewiz 8y ago
      MS is going where developers are, and outside MS there is no community around SF. Hired one of K8S founders, built new products around k8s, advocates docker left and right at conferences, these are clear signals that the tech doesn’t have a future
      - deleted 8y ago
        [deleted]
      - youdontknowtho 8y ago
        SF can also manage docker containers. They are doing lots of work with k8s, but this system has a huge amount of internal usage and has provably been used to build global scale services. Its strengths are different than k8s and the distributed system space has lots of options. You (and others) seem to be enjoying some schadenfruede about SF not "winning" some competition. I don't think the world works that way. Lots of people will use it for big applications. More people will probably use something else. That's about it. The type of comment you made doesn't get marked by the moderators for some reason even though it doesn't actually provide any insight. The article had detailed information about the internals of how it worked. That's the interesting thing here. The Ziff Davis style dev-adoption-horse race is pretty pointless.
s2g 8y ago
Service fabric is open source. Not locked to one vendor. Http://github.com/Microsoft/service-fabric
benaadams 8y ago
> SF is only available from one vendor, whereas K8S is available almost anywhere. SF is open source on GitHub and you can run it on-premise or on any cloud, Windows or Linux. The tooling is probably easier on Azure; but you can also happily run it on AWS; as well as the Service Mesh variant which is sort of "Serverless Clusters" or "Clusterless Clusters", applying the strange naming of "Serverless".

by wenc 8y ago

manigandham 8y ago

Service Fabric is different from Kubernetes. It's not a container orchestration platform but a full-stack distributed state and processing system with components that can serve as the foundation for building something like Kubernetes itself. The naming is confusing and there is a Service Mesh offering from Azure that lets you run your own applications easily if they're using the Service Fabric framework already, but SF can run containerized code in any language, and it has bindings for C# and Java (for now) if you want to use the primitives directly. SF is also now open-source and you can run it all yourself in whatever environment you want: https://github.com/Microsoft/service-fabric https://github.com/Microsoft/service-fabric

dewiz 8y ago
SF has been opensourced very late though [1], to get some attention and trying to survive. Legitimate but very different from being an open source project. The cross-platform support is very weak [2][3], far from K8S, Mesos and Swarm developer friendliness. [1] https://blogs.msdn.microsoft.com/azureservicefabric/2018/03/14/service-fabric-is-going-open-source https://blogs.msdn.microsoft.com/azureservicefabric/2018/03/... [2] https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started-mac https://docs.microsoft.com/en-us/azure/service-fabric/servic... [3] https://social.msdn.microsoft.com/Forums/en-US/b5045fe1-51a2-4c58-ae90-53c145d3ef59/using-mac-with-azure-service-fabric https://social.msdn.microsoft.com/Forums/en-US/b5045fe1-51a2...
- manigandham 8y ago
  Trying to survive? It already runs all of Microsoft's cloud services and does just fine. Open-sourcing was more of a good-will move so that the community can also use it, similar to how Apple released FoundationDB. The links you point to are about developing with SF, which doesn't natively run on Mac OSX. It can run on Linux but has fewer features for now, but this is being worked on. It's not the same as K8S/Mesos/Swarm though so if container orchestration is all you need then you shouldn't use SF.
- polskibus 8y ago
  I don't think it's buildable on Windows yet. It's been like this for a couple of months now, not sure if MS is really trying to get others involved.
  - dewiz 8y ago
    MS is going where developers are, and outside MS there is no community around SF. Hired one of K8S founders, built new products around k8s, advocates docker left and right at conferences, these are clear signals that the tech doesn’t have a future
    - deleted 8y ago
      [deleted]
    - youdontknowtho 8y ago
      SF can also manage docker containers. They are doing lots of work with k8s, but this system has a huge amount of internal usage and has provably been used to build global scale services. Its strengths are different than k8s and the distributed system space has lots of options. You (and others) seem to be enjoying some schadenfruede about SF not "winning" some competition. I don't think the world works that way. Lots of people will use it for big applications. More people will probably use something else. That's about it. The type of comment you made doesn't get marked by the moderators for some reason even though it doesn't actually provide any insight. The article had detailed information about the internals of how it worked. That's the interesting thing here. The Ziff Davis style dev-adoption-horse race is pretty pointless.

s2g 8y ago

Service fabric is open source. Not locked to one vendor. Http://github.com/Microsoft/service-fabric

benaadams 8y ago

> SF is only available from one vendor, whereas K8S is available almost anywhere. SF is open source on GitHub and you can run it on-premise or on any cloud, Windows or Linux. The tooling is probably easier on Azure; but you can also happily run it on AWS; as well as the Service Mesh variant which is sort of "Serverless Clusters" or "Clusterless Clusters", applying the strange naming of "Serverless".