What are the differences between Container (Docker), App Service and Service Fabric in Azure?

3

When we publish an application, service or Web API we have a great diversity of options today. I particularly like Azure because of its mentality of facilitating the settings by the panel and passing the complexity to other parts of the application (when possible).

In this respect, I was left wondering about the latest Azure options. In the Azure documentation it seems to me that several services can serve the same need.

What are the differences between publishing an application, service, or Web API in the following tools?

  • Azure Container service

  • Azure Service Fabric

  • Azure Application Service

asked by anonymous 15.08.2017 / 22:43

1 answer

2

Although you get some identical results with the 3 options, you need to evaluate the scenario that best fits your problem, since it does not make much sense to upload a simple site with Container or Service Fabric.

Azure Container Service

The Azure Container Service makes it easy to create, configure, and manage a cluster of preconfigured virtual machines to run container applications. It uses an optimized configuration of popular open source programming and orchestration tools. This allows you to use your existing skills or leverage a large and growing body of community experience to deploy and manage container-based applications in Microsoft Azure. One of the good reasons to use Container is:

  • Similar Environments
  • Application as a complete package
  • Standardization and replication
  • You need an infrastructure that can be scaled up or down based on the needs of each application.
  • You need fast deployments in all your environments.
  • Ensure that there is no dependency on your application, since everything is already inside the container.
  • If you have experience with some orchestration solutions such as Docker, Swarm, Google Kubernetes.

Follow some links to better understand how Azure Conteiner Service works

Azure Service Fabric

Azure Service Fabric is a distributed systems platform that facilitates the packaging, deployment and management of scalable and reliable microservices and containers. Developers and administrators can avoid complex infrastructure problems and focus on deploying critical and demanding workloads that are scalable, reliable, and manageable. One of the good reasons to use Azure Service Fabric:

  • When we need large-scale services
  • When we need highly available services
  • When we need services easily scalable
  • When we need session-based interactive services
  • When we need services with high flow of data analysis
  • When we need services for data collection and IoT processing
  • When we need to deploy services in a simple way both in the cloud and local (OnPremise).

Follow some links to better understand how Azure Service Fabric works

Azure Application Service

It is a PaaS platform, ideal for deploying systems for various platforms, from Web applications, WebAPI, WebSites, etc. All of this can be used in .NET, Java, Node.js, Php and Python platforms. When we talk about Applications, we refer to the hosting features. Among the benefits of the Azure Application Service, here are a few:

  • Support for various languages and structures
  • DevOps Optimization
  • Connections with SaaS platforms
  • Pre-configured application templates such as Wordpress, Joomla, Drupal, etc.

With Azure Application Services you can deploy the following types of applications:

  • Applications / Web Sites
  • Mobile applications as backend hosting
  • RESTful type API
  • Logical Applications such as Azure Functions

Follow some links to better understand how Azure Service Fabric works

Conclusion

We can host a simple site with Conteiner Services, Service Fabric or Application Service, but with Conteiner and Service Fabric, it requires a certain configuration of environment, no type of environment configuration is required in the Azure Application Service.

    
24.08.2017 / 20:05