All geek questions in one place

Benefits of Fabric Microservices vs Azure Cloud Services / Web Application Collection

I have an application that can be divided into several communication services. My current implementation is monolithic, and I want to reorganize it so that individual components can be deployed, iterated, and scaled independently. I see two ways to do this with Azure:

  1. Service Fabric Service, consisting of a set of interacting microservices (stateless, web-api, etc.)
  2. A set of separate Azure web applications / cloud services that call each other at http endpoints.

Are there any obvious advantages of 1 over 2? Any rule of thumb to choose one over the other would also be very helpful.

+4
source share
2 answers

I think this page compares it well: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cloud-services-migration-differences/

I can’t say it better than that.

Actually there is no right rule. Service fabric may seem more complex, but it offers some things that Cloud Services / Web Apps do not.

Brief summary (taken from the provided link):

- , Windows Linux, - Azure . Service Fabric :

  • . . Service Fabric , , Service Fabric. .
  • . VM . Service Fabric , , , .
  • Service Fabric , Windows Server Linux, , Azure . , .
  • . Service Fabric - , , .
+14

. :

  1. , Service Fabric. micros, Service Fabric - . , ,

    • . , , .
    • , ) , ; ) , !

  2. /DC , Service Fabric . , DC , Service Fabric, . .

0

Source: https://habr.com/ru/post/1655317/

More articles:


All Articles