Azure Service Fabric is designed to provide extensible support to full application lifecycle and also at the same time for the CI / CD of cloud applications that includes containers as well.
Lifecycle of an application on Azure Service Fabric can be thought of development, deployment, daily management and finally maintenance leading the decommissioning.
The abilities and capabilities of Service Fabric’s application lifecycle management enables application administrators, IT operators to engage with its simple, workflows to provision, deploy, patch and finally to monitor their applications.
The built-in support features as like the workflows reduce the overhead on the IT operators in keeping the applications highly available.
Many of the applications that are designed and developed with Azure’s Service Fabrice contains a unique combination of stateless and stateful micro-services and containers (along with other executables which are put together along with all these artifacts).
Azure Service Fabric allows the deployments of applications as multiple instances. Each of the instances thus deployed can be managed and upgraded independently without any dependencies.
Basically the main importance of deploying applications through Azure’s Service Fabric allows them to be done in containers to make them highly reliable.
Any of the .NET, ASP.NET Core, Nodejs, Windows / Linux containers, Java Virtual Machines, Scripts, Angular JS and for that case any other thing that can possibly make your application can be deployed by Azure’s Service Fabric.
CI / CD tool as like Visual Studio Team Services, Jenkins, Octopus Deploy are all integrated with Azure’s Service Fabric, which enables it to be used with any other popular CI / CD tool.
Source: MindMajix