This document discusses microservices and Azure Service Fabric. It provides an overview of architectural evolutions from monolithic to service-oriented to microservices. Azure Service Fabric is presented as a platform for developing microservices that provides high availability, scalability and reliability. Key concepts are defined including nodes, clusters, stateful and stateless services. The presentation concludes with a demonstration of creating an Azure Service Fabric cluster and deploying an application.

1. Microservices
Azure Service Fabric

2. Agenda
• Evolution of Architectures
• Why Azure Service Fabric
• How Azure Service Fabric Works
• Key Terminologies in Service Fabric
• Demo using Azure Service Fabric Cluster

3. My Intro
• Baskar Rao
• Senior .Net Consultant with Compunnel Software Group.
• https://www.linkedin.com/in/baskarrao-dandlamudi
• baskarrao.dandlamudi@outlook.com
• www.compunnel.com

4. Evolution of Architectures
• Monolithic Architecture (3- Tier Architecture/ n-Tier Architecture)
• Pros
 Simpler to design
 Faster communication between components
• Cons
 Tightly Coupled Design
 Unable to scale individual components.

5. Evolution of Architectures
• Service Oriented Architecture(SOA)
• Pros
 Simpler to design
 Loosely Coupled Design
 Language Interoperability
• Cons
 Services can be scaled with additional cost in infrastructure
 Change in service definition requires changes in the consumer
 More plumbing code to integrate services

6. Evolution of Architectures
• Micro services Architecture
• Pros
 Easy to scale, test, deploy and manage services.
 Most of the services are REST based with less plumbing code.
 More granular services and loosely coupled.
 Perform small and quick operations of business.
• Cons
 Increased number of entities to track
 Developing chatty applications leads to performance problems
 Increased network latency between calls.
 Increased design time to identify and isolate data stores.

7. Why Azure Service Fabric?
• Microsoft runs the entire azure service over
Azure Service Fabric.
• This is an offering from Microsoft to develop
Microservices and containers.
• Used to design and develop highly available
and durable micro services.

8. Why Azure Service Fabric?
• Developers and Administrators can focus on
developing applications avoiding infrastructure
downtimes due to updates and upgrades
• Guarantees application availability.
• Controls the density of applications in cluster
• Provides feature to develop stateful workload
stateless services with
separate stores
stateful
services
stateless
presentation
services

9. How Azure Service Fabric Works
• Enables Secure Communications
• Clusters the different nodes into
a single entity (named clusters)
so that Service Fabric can detect failures,
perform leader election,
and provide consistent routing
• Reliability of Service Fabric services
through mechanisms such as replication,
resource management, and failover

10. How Azure Service Fabric Works
• Hosting SubSystem manages lifecycle
of application in node.
• Management Subsystem manages the
lifecycle of applications and services
• Testability subsystem helps application
developers test their services
through simulated faults

11. Key Terminologies
• Node
A machine or VM that is part of a cluster is
called a node.
• Cluster
Datacenter (Azure, On-Premises, Amazon)
Load
Balanc
er
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/?)

12. Key Terminologies
• Stateful Services
Use a stateful service when you want Service Fabric
to manage your service's state via its Reliable Collections
or Reliable Actors programming models
• Stateless Services
Use a stateless service when the service's
persistent state is stored in an external storage
service such as Azure Storage,
Azure SQL Database, or Azure Cosmos DB.
stateless services with
separate stores
stateful
services
stateless
presentation
services

13. Key Terminologies
• Reliable Dictionary
Used as data store for stateful services
• Partitions
Data stored in service fabric is distributed
across nodes in the fabric
stateless services with
separate stores
stateful
services
stateless
presentation
services

14. ASP.Net Core WebHost in Service Fabric
Service host process
Service instance/replica (multiple)
ASP.NET Core

15. Demo Using Service Fabric
• Use the below url to create a free service fabric cluster
https://try.servicefabric.azure.com/
• Service Fabric Cluster Explorer
• Deploy an application to Service Fabric Cluster
• Perform an update and re-deploy code to Service Fabric Cluster

16. • Thanks to the organizers of Columbus Code Camp
for giving me an opportunity to present.
• I would also like to thank Doug Mair, Principal Consultant
with Improving for guiding me in making this happen.

17. Questions
https://www.linkedin.com/in/baskarrao-dandlamudi
baskarrao.dandlamudi@outlook.com
https://baskarrao.wordpress.com/