Welcome to a session where we will talk about the most important thing that we need to know about Azure Service Fabric and microservices. This presentation will introduce you in the most important concept of Azure Service Fabric with real life examples and demos. This is not a how to session, this is a session with the pillars of Azure Service Fabric.

2. First 13 steps to be able to
design an application for
Azure Service Fabric
@RaduVunvulea

3. 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

6. Monolithic systems

7. Things started to evolve

8. … and evolve

9. Team responsability
Product Team
<<Needs to know each
part of the system>>

10. Microservices
<< software architecture style in which complex
applications are composed of small, independent
processes communicating with each other using
language-agnostic APIs>>

11. Microservices
High decoupled
Small
Easy to replace
Symmetrical architecture
Focus on doing a small task
Independent deployment units

13. Service Fabric
Build and operate always-on, hyper-scale
services

14. Capabilities

15. Overview

16. Service Type

17. Service Type
Reliable
Services
Reliable
Actors
Stateful
Stateless

18. Reliable Service and Actor
ReliableService
• Classical
service
• Reliable
• Available
• Scalable
ReliableActor
• State
• Turn-base
access
• Single
thread
• Reentrancy

19. Stateless and Stateful
Stateless
• No state
persisted
between
calls
Stateful
• ‘A’ state
is
persisted
between
calls

22. Lifecycle

23. Reliable
Services
Reliable
Actors
Stateful
Stateless
First call…

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

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

26. Reliable Collections

27. • Low latency
• High-throughput
• Isolation Level
• Snapshot
• Repeatable Read
• Can be used only
with Reliable Stateful Services
Reliable Collections
Dictionary
and
Queue
Replicated
Persisted
In-memory
<<service
instance>>
Asynchronous
Transactional

28. Where collection are stored

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

32. •
•

33. Timers and Reminders
(Actor only)

34. 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

35. Concurrency

36. Events and Reentrancy
(Actor only)

37. Events Reentrancy
• Send notifications
• Should be used only
for actor-client
communication
• Allows actors to
reentrant when is
the same call
context chain
• Can be controlled
(ReentrancyMode)

39. Register
Call the event from our actor

40. Partitioning & Replication

41. Partitioning
Similar with Data Partitioing and Sharding

42. Replication

43. Failover Manager & Upgrade Domains

44. ... at what level
Application
• Partitioning
• Replication
Cluster
• Fault Domain
• Upgrade Domain
• Naming Service
• Resource
Balancer
• Failover
Manager

46. Service Affinity

47. Service Affinity
• Give us the possibility to ensure that 2 different
services are running on the same machine
• Useful for migration scenarios (legacy applications)
• Limitations
• Services of the same type (stateless or stateful)
• Stateless services need to have the same instance count
• Stateful services need to have the same replica number
• Cannot be used in combination with partitioning

48. Service Affinity
<ServiceTemplates>
<StatelessService ServiceTypeName=“PaymentService" InstanceCount=“8">
<SingletonPartition />
</StatelessService>
…
</ServiceTemplates>
<ServiceTemplates>
<StatelessService ServiceTypeName=“CardTransactionService" InstanceCount=“8">
<SingletonPartition />
<ServiceCorrelations>
<ServiceCorrelation Scheme="Affinity" ServiceName="fabric:/shopApp/paymentService"/>
</ServiceCorrelations>
</StatelessService>
</ServiceTemplates>

49. Service Affinity
<ServiceTemplates>
<StatelessService ServiceTypeName=“PaymentService" InstanceCount=“8">
<SingletonPartition />
</StatelessService>
…
</ServiceTemplates>
<ServiceTemplates>
<StatelessService ServiceTypeName=“CardTransactionService" InstanceCount=“8">
<SingletonPartition />
<ServiceCorrelations>
<ServiceCorrelation Scheme="Affinity" ServiceName="fabric:/shopApp/paymentService"/>
</ServiceCorrelations>
</StatelessService>
</ServiceTemplates>
<ServiceTemplates>
<StatelessService ServiceTypeName=“UserCheckService" InstanceCount=“8">
<SingletonPartition />
<ServiceCorrelations>
<ServiceCorrelation Scheme="Affinity" ServiceName="fabric:/shopApp/cardTransactionservice"/>
</ServiceCorrelations>
</StatelessService>
</ServiceTemplates>

50. What can we run in
Service Fabric?

51. What can we run?
Service Fabric
Web Sites
Application
Custom
logic

52. How
• 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

53. Conclusion

54. Conclusion
• Reliable Service vs Reliable Actor
• Stateless vs Stateful
• Timers and Reminders
• Lifecycle and GW
• Different solutions for the same problem
• Scalable, High Available, Flexible, Secure

55. Question
Answers

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

57. Today: Enjoy the day
Tonight: Take a look on
https://github.com/Azure/
servicefabric-samples
What’s next?

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