Not to mention that as well as being
more advanced, Service Fabric is way way easier to work with than Kubernetes. It's a no brainer if you use Azure or Azure Stack.
A curious feature of Microsoft's cloud platform is that it has two fundamentally different platforms for microservices. One is based on the homegrown Service Fabric, while the other is orchestrated by the Google-originated Kubernetes, available on Azure through the Azure Kubernetes Service (AKS). Both are open source. How …
And the Microsoft Azure Service Fabric is conceptually a generation BEHIND the Paremus Service Fabric.
The Paremus Service Fabric an OSGi based runtime adaptive platform that can dynamically assemble runtime adaptive OSGi /Java applications!! As well as support your boring Docker Container Image REST Services written in any language you like.
"One is based on the homegrown Service Fabric, while the other is orchestrated by the Google-originated Kubernetes, available on Azure through the Azure Kubernetes Service (AKS). Both are open source.
How should developers choose, The Reg asked Jason Zander, the executive veep in charge of Azure"
EASY. One is designed to lock you into Azure, the other is designed to avoid vendor lock-in :-)
Biting the hand that feeds IT © 1998–2020