The document compares Azure Cloud Services (Web & Worker Roles) to Azure Service Fabric. It notes that Cloud Services have each role/instance run on a separate VM, making deployment, upgrades, and scaling slower. Service Fabric runs multiple service instances together on the same VM, making deployment, upgrades, and scaling faster. It also allows for thousands of service nodes and a development cluster using OneBox.

2. Luis Valencia – MVP
www.luisevalencia.com
Twitter: @levalencia

24. Azure Cloud Services
(Web & Worker Roles)
Azure Service Fabric
(Services)
• Each role/instance per VM
• Slow deployment & upgrades
• Slow to scale role instances up/down
• Emulator for development
• Many service instances share a PC/VM
• Fast deployment & upgrades
• Fast to scale service instances up/down
• OneBox cluster for development

25. Datacenter (Azure, Amazon, On-Premises, …)
Load
Balancer
PC/VM #1
Service Fabric
Your code, etc.
PC/VM #2
Service Fabric
Your code, etc. PC/VM #3
Service Fabric
Your code, etc.
PC/VM #4
Service Fabric
Your code, etc.
PC/VM #5
Service Fabric
Your code, etc.
Your code, etc.
(Port: 19080)
Web Request
(Port: 80/443/?)
*SF supports 1,000s of nodes

26. Node #1
F
Node #2
C N I
Node #3
C F
Node #4
N I
Node #5
C
I
F
N
U
U
U
N F U
IC

27. PC/VM
FabricHost.exe
[Auto-starts at boot]
Fabric.exe
[Inter-node communication]
Your App’s Services
Ex: ASP.NET or other .exe
[Exposes public endpoint(s)]
FabricGateway.exe
[Cluster communication]
N
o
d
e
OneBox
[testing]
Fabric.exe
[Inter-node communication]
Your App’s Services
Ex: ASP.NET or other .exe
[Exposes public endpoint(s)]
FabricGateway.exe
[Cluster communication]
N
o
d
e

33. #

34. Luis Valencia – MVP
www.luisevalencia.com
Twitter: @levalencia