The document discusses microservices and Azure Service Fabric, explaining that microservices break applications into small, independent processes that communicate through APIs and Service Fabric is a platform for building and managing microservices applications both on-premises and in the cloud. It provides an overview of Service Fabric concepts like service types, the service lifecycle, and reliable collections.

1. @ITCAMPRO
Azure Microservices in Practice
Solution Architect , Microsoft Azure MVP
iQuest Technologies
@Radu Vunvulea

2. @ITCAMPRO

3. @ITCAMPRO
RADU VUNVULEA MCTS MCP BANK HOME AUTOMATION
MVP ENTERPRISE
AUTOMOTIVE PHARMA
LEAN AND AGILE E-COMMERCE
WEB iQuest
AZURE JAVASCRIPT VUNVULEARADU.BLOGSPOT.COM
MOBILE DOTNET @RaduVunvulea
WCF WPF ENTHUSIASTIC

4. @ITCAMPRO
Scope

5. @ITCAMPRO
WHAT ARE MICROSERVICES?

6. @ITCAMPRO

7. @ITCAMPRO
Software architecture style in which complex
applications are composed of small, independent
processes communicating with each other using
language-agnostic APIs
Microservices

8. @ITCAMPRO
WHY WE SHOULD USE
MICROSERVICES?

9. @ITCAMPRO
If we need a system that has components that are…
High decoupled
Small
Easy to replace
Focus on doing a small task
Independent deployment units
Symmetrical architecture

10. @ITCAMPRO
Evolution
Maintenance
is hard
Adding new
features is slow
Changes are
expensive
Technology
becomes the
obstacle rather
than enabler
App Modernization

11. @ITCAMPRO
(AZURE) SERVICE FABRIC

12. @ITCAMPRO
• Service Fabric
• Azure Service Fabric
Why we have two different things?
?

13. @ITCAMPRO
Service Fabric | Azure Service Fabric
Microservices
Cloud
Azure
Azure Service
Fabric
AWS Service Fabric
On-premises Service Fabric

14. @ITCAMPRO
Overview
Service Fabric
Azure
Windows
Server
Linux
On-premises
Windows
Server
Linux
Hosted clouds
Windows
Server
Linux
Micros
ervice
Micros
ervice
Micros
ervice
Micros
ervice
Micros
ervice

15. @ITCAMPRO
SERVICE TYPE

16. @ITCAMPRO
ReliableService •Classical
service
•Reliable
•Available
•Scalable
Actor
•State
•Turn-base
access
•Single
thread
•Reentrancy

17. @ITCAMPRO
Stateless •No state
persisted
between
calls
Stateful
•‘A’ state
is
persisted
between
calls

18. @ITCAMPRO

19. @ITCAMPRO
What can we run in Service Fabric?
Service Fabric
Web Sites
Application
Custom
logic

20. @ITCAMPRO
• Multiple programing languages (C# & Java)
• Support different commucation mechanisms:
–HTTP(s)
–WCF
–TCP
–UDP
• Any protocol and communication stack is supported
• Capable to run a guest executable
How

21. @ITCAMPRO

22. @ITCAMPRO
SERVICE LIFECYCLE

23. @ITCAMPRO
Reliable
Services Actors
Stateful
Stateless
State
StateState
First call…
Reliable
Collections

24. @ITCAMPRO
Reliable
Services Actors
Stateful
Stateless
State
State
… after the call is executed
State

25. @ITCAMPRO
Reliable
Services Actors
Stateful
Stateless
State
State
… when GC is triggered
State

26. @ITCAMPRO

27. @ITCAMPRO
One UI for all environments

28. @ITCAMPRO
DEBUGGING AND TRACING

29. @ITCAMPRO
• Local debugging like any other .NET application
• Attach debugger to any Service Fabric Application
(on-premises or cloud)
• Diagnostic Events persistent in Cluster
• Real time Streaming Traces (Diagnostics Events)
Debugging and tracing

30. @ITCAMPRO

31. @ITCAMPRO
• Low latency
• High-throughput
• Transactional
• Can be used only
with Reliable Services
Reliable Collections
Dictionary
and
Queue
Replicat
ed
Persiste
d
In-
memory
<<servic
e
instance
>>
Asynchr
onous
Transacti
onal

32. @ITCAMPRO
Where collection are stored

33. @ITCAMPRO
• Different instances of the same
service can access the same
Reliable Collection
• Instances from different
services cannot access the
same collection
Reliable Collection – visibility

34. @ITCAMPRO

35. @ITCAMPRO
TIMERS AND REMINDERS

36. @ITCAMPRO
Timers and Reminders
Timers
Similar with .NET
Called at a specific
time interval
Reminders
Timer with
persistence
Trigered in all
circumstances
(deactivations and
failovers)
Concurrency
Turn based
concurrency
Stateful Actos only

37. @ITCAMPRO
• Context: Multiple calls to the same Reliable Actor
Concurrency

38. @ITCAMPRO
Concurrency

39. @ITCAMPRO
Concurrency

40. @ITCAMPRO
Execution flow:
• Reminder Trigger
• SetPrice
• SetStock
Concurrency

41. @ITCAMPRO

42. @ITCAMPRO
Events
• Send events and
notifications from
services to caller
• Allows us be notified at
different steps on when
an exception occurs
• Can be used only for
actor-client
communication

43. @ITCAMPRO
• On Actor:
– IActorEvents
– Trigger our custom events
• On source:
– Implement callback (Event Handler)
– Subscribe our Event Handler
Events

44. @ITCAMPRO

45. @ITCAMPRO
TRACING AND DEBUGING

46. @ITCAMPRO
BEHIND THE SCENE

47. @ITCAMPRO
Partition and Replication

48. @ITCAMPRO
Fault Domains and Upgrade Domains

49. @ITCAMPRO
Where we can control them
Application
• Partitioning
• Replication
Cluster
• Fault Domain
• Upgrade Domain
• Naming Service
• Resource
Balancer
• Failover Manager

50. @ITCAMPRO

51. @ITCAMPRO
Question
Answers

52. @ITCAMPRO
{
“name” : “Radu Vunvulea,
“blog” : “vunvulearadu.blogspot.com”,
“email” : ”vunvulear@outlook.com”,
“socialMedia” :
{
“twitter” : “@RaduVunvulea”,
“fb” : “radu.vunvulea”
}
}