1. Azure Service Fabric Mesh
Udaiappa Ramachandran ( Udai )
LinkedIn://linkedin.com/in/udair
Twitter: @nhcloud

3. Who am I?
• Udaiappa Ramachandran ( Udai )
• CTO, Akumina, Inc.,
• Consultant
• Focus on Cloud Computing
• Microsoft Azure, Amazon Web Services and Google
• New Hampshire Cloud User Group (http://www.meetup.com/nashuaug )
• http://cloudycode.wordpress.com
• @nhcloud

4. Agenda
• Introduction to Service Fabric (SF)
• SF Environments
• Service Fabric Mesh
• SF Mesh Resource Model
• How does it work?
• Things to Know
• Demo
• References

5. Service Fabric (SF)
• Cluster (network connected set of VMs or Physical Servers)
• Application platform for building Microservices
• Native programming model
• Reliable Actors, Reliable Services
• Containers, ASP.NET CORE, GUEST EXECUTABLE
• Microsoft Products
• Azure DocumentDB, Intune, Skype for Business, Bing Cortana, Azure Event Hubs, Azure SQL
Database
• Cluster Security (enabled at cluster creation time)
• Stateless and Stateful support
• State and Application life cycle management with monitoring

6. SF Environments
• Service Fabric Mesh
• Azure Service Fabric
• Service Fabric standalone
• Service Fabric Development cluster

7. SF Mesh
• Focus on application not the infrastructure like PaaS
• Fully managed cluster (code named Seabreeze)
• Application platform use of container
• Actors and Reliable Collections will be exposed part of mesh
• Per Second Billing for AKS/ACS/Mesh
• Ability to deploy from CICD
• Auto Scaling
• Blue/Green deployments
• Serverless notion

8. SF Resource Model
• Application
• Service
• Code Package (Containers)
• Network
• Routes
• Gateway
• Secrets
• Volume (Azure File Storage Vs Reliable Disk)

9. How does it work?
Source: https://www.youtube.com/watch?v=P-VmFhh2XJk

10. Things to know in Preview
• Quota
• Number of applications: 5
• Cores per application: 12
• Total RAM per application: 48 GB
• Network and Ingress end points: 5
• Azure Volumes that you can attach: 10
• Number of Service replicas: 3
• The largest container you can deploy is limited to 4 cores and 16GB RAM.
• You can allocate partial cores to your containers in increments of 0.5 cores, up to a maximum of
6 cores.
• Services can run continuously 48 hours after that it will be shutdown
• HNA failed with error

11. Key Commands to Deploy App
1. az login
2. az account set --subscription "<subscriptionName>"
3. az acr repository list --name <ACR-NAME>
4. docker build -t <SERVICENAME> .
5. docker tag <SERVICENAME> <ACR-NAME>.azurecr.io/<SERVICENAME>:1.0
6. az acr login -n <ACR-NAME>
7. docker push <ACR-NAME>.azurecr.io/<SERVICENAME>:1.0
8. az mesh deployment create --resource-group <RESOURCEGROUPNAME> --template-file
c:tempmesh_rp.windows.json --parameters c:tempmesh_rp.windows.parameters.json
9. az mesh gateway show --resource-group <RESOURCEGROUPNAME> --name
<GATEWAYNAME>
10. az mesh app show --resource-group <RESOURCEGROUPNAME> --name <SFAPPNAME>
11. az mesh code-package-log get --resource-group <RESOURCEGROUPNAME> --application-
name <SFAPPNAME> --service-name <SERVICENAME> --replica-name 0 --code-package-
name <CODEPACKAGENAME>

12. Demo
• Pre-Requisites
• Building deploying from Visual Studio
• Deploying existing application using CLI
• Scale and Upgrade

13. References
• https://github.com/Azure-Samples/service-fabric-mesh
• https://aka.ms/sfmeshpreview
• https://docs.microsoft.com/en-us/azure/service-fabric-mesh/
• https://docs.microsoft.com/en-us/rest/api/servicefabric/sfmeshrp-index
• https://docs.microsoft.com/en-us/azure/service-fabric/
• https://azure.microsoft.com/en-us/updates/?category=service-fabric-mesh

14. Thank you for attending
BOSTON Code Camp
31(#bocc)