4 ms·

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

by 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.
    - polskibus 8y ago
      I have to say, I'm evaluating some of the .net technologies for building distributed systems, namely Akka.NET, Orleans and SF, and using any of them requires quite a lot of investment and therefore time to learn to use them right. The last thing I want to experience is that after a year or two, the tech I pick is going to be abandoned or at least put into maintenance mode. Therefore I'd appreciate all insights (if possible data-driven) on the future plans about SF and how does it stack against k8s investments by MS. It would be great if MS themselves made an official announcement. Seeing that SF doesn build on Windows for several months, makes me doubt whether the momentum behind open sourcing SF is real.
      - CuriousSkeptic 8y ago
        Theres a good presentation from the Build conference about the future. In summary they will add the hosted “mesh” variant. And move the SDK towards polyglot libs for use in docker containers instead of a C# framework. The reliable collections part of the SDK will be just a lib providing storage for abitrarily shaped data needing replication. They also mean to hav it all work similarity for your own clusters on-perm or on azure. (And some one asked, yes managed service principles and secrets is coming up in 6.3 probably) P.s There is also a regular q/a session over Skype they record and put on YouTube if you want more details or ask questions directly

by dewiz 8y ago

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.
  - polskibus 8y ago
    I have to say, I'm evaluating some of the .net technologies for building distributed systems, namely Akka.NET, Orleans and SF, and using any of them requires quite a lot of investment and therefore time to learn to use them right. The last thing I want to experience is that after a year or two, the tech I pick is going to be abandoned or at least put into maintenance mode. Therefore I'd appreciate all insights (if possible data-driven) on the future plans about SF and how does it stack against k8s investments by MS. It would be great if MS themselves made an official announcement. Seeing that SF doesn build on Windows for several months, makes me doubt whether the momentum behind open sourcing SF is real.
    - CuriousSkeptic 8y ago
      Theres a good presentation from the Build conference about the future. In summary they will add the hosted “mesh” variant. And move the SDK towards polyglot libs for use in docker containers instead of a C# framework. The reliable collections part of the SDK will be just a lib providing storage for abitrarily shaped data needing replication. They also mean to hav it all work similarity for your own clusters on-perm or on azure. (And some one asked, yes managed service principles and secrets is coming up in 6.3 probably) P.s There is also a regular q/a session over Skype they record and put on YouTube if you want more details or ask questions directly