Microsoft’s Azure platform services have always offered . In fact, has been there from the start. Initially supporting Azure’s SQL services, it’s now a foundation of much of the Azure platform, along with .

You’ve been able to use Azure Service Fabric in your own applications for nearly as long, because it’s key to managing and scaling your own code. With support for containers and virtual infrastructure, you can compare it with other service orchestration tools like . Although powerful, it’s not that intuitive to use; its complex set of XML-based configuration files can get in the way of building a deployment and can be hard to debug.

is meant to fix that difficulty of use, building on lessons from Kubernetes to simplify configuring and deploying applications built up of container-hosted microservices and of Azure’s own platform services.

Introducing Azure Service Fabric Mesh

Azure Service Fabric Mesh is , using either ASP.Net Core or console applications. But it also lets you develop and host code in any language that’s supported by a Docker container, so you can work with languages that have a more distributed systems focus, such as . Azure’s underlying platform flexibility makes this an alternative to other microservices frameworks, as well as removing the need to build and manage service orchestration around your code.