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.
Use of FIDO in the Payments and Identity Landscape: FIDO Paris Seminar.pptx
First 13 steps to be able to design an application for Azure Service Fabric
1.
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
10. Microservices
<< software architecture style in which complex
applications are composed of small, independent
processes communicating with each other using
language-agnostic APIs>>
18. Reliable Service and Actor
ReliableService
• Classical
service
• Reliable
• Available
• Scalable
ReliableActor
• State
• Turn-base
access
• Single
thread
• Reentrancy
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
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
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)
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
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
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