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

Asked

Viewed 249 times

3

When we publish an application, service or Web API we now have a wide range of options. I particularly like Azure for its mindset of facilitating settings across the dashboard and shifting complexity to other parts of the application (when possible).

In this respect, I have some doubts about the most recent options offered by Azure. In the Azure documentation it seems to me that several services can meet 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 Service of application

1 answer

2


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

Azure Container Service

Azure Container Service makes it easy to create, configure and manage a cluster of preconfigured virtual machines to run containerized 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 across all your environments.
  • Ensure that no dependency on your application is lacking as everything is already inside the container.
  • If you have experience with some orchestration solutions like Docker, Swarm, Google Kubernetes.

Follow a few links to better understand how Azure Conteiner Service works

Azure Service Fabric

Azure Service Fabric is a distributed system 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 implementing 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 easily scalable services
  • When we need session-based interactive services
  • When we need services with high data analytics flow
  • When we need services for data collection and Iot processing
  • When we need to deploy services simply in the cloud and locally (Onpremise).

Follow a few links to better understand how Azure Service Fabric works

Azure Application Service

It is a platform of the type Paas, ideal to deploy systems for several platforms, since Web applications, Webapi, Websites, etc... All this can be used in the platforms . NET, Java, Node.js, Php and Python. When we talk about Apps, we refer to hosting features. Among the benefits of the Azure App Service, here are some:

  • Support for multiple languages and structures
  • Optimization of Devops
  • Connections with Saas platforms
  • Application Templates preconfigured as Wordpress, Joomla, Drupal, etc..

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

  • Applications / Web Sites
  • Mobile apps like backend hosting
  • Restful type API
  • Logical Applications like Azure Functions

Follow a few links to better understand how Azure Service Fabric works

Completion

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

Browser other questions tagged

You are not signed in. Login or sign up in order to post.