Download to read offline
Uploaded byRadu Vunvulea
Azure Microservices in Practice - Radu Vunvulea ITCamp Community Timisoara 07/12/2016
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.
More Related Content
Similar to Azure Microservices in Practice - Radu Vunvulea ITCamp Community Timisoara 07/12/2016
Azure Microservices in Practice - Radu Vunvulea ITCamp Community Timisoara 07/12/2016
- 1. @ITCAMPRO Azure Microservices inPractice Solution Architect , Microsoft Azure MVP iQuest Technologies @Radu Vunvulea
- 2.
- 3. @ITCAMPRO RADU VUNVULEA MCTSMCP 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.
- 5.
- 6.
- 7. @ITCAMPRO Software architecture stylein which complex applications are composed of small, independent processes communicating with each other using language-agnostic APIs Microservices
- 8. @ITCAMPRO WHY WE SHOULDUSE MICROSERVICES?
- 9. @ITCAMPRO If we needa 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 featuresis slow Changes are expensive Technology becomes the obstacle rather than enabler App Modernization
- 11.
- 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.
- 15.
- 16.
- 17. @ITCAMPRO Stateless •No state persisted between calls Stateful •‘A’state is persisted between calls
- 18.
- 19. @ITCAMPRO What can werun in Service Fabric? Service Fabric Web Sites Application Custom logic
- 20. @ITCAMPRO • Multiple programinglanguages (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.
- 22.
- 23.
- 24. @ITCAMPRO Reliable Services Actors Stateful Stateless State State … afterthe call is executed State
- 25. @ITCAMPRO Reliable Services Actors Stateful Stateless State State … whenGC is triggered State
- 26.
- 27. @ITCAMPRO One UI forall environments
- 28.
- 29. @ITCAMPRO • Local debugginglike 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.
- 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.
- 33. @ITCAMPRO • Different instancesof the same service can access the same Reliable Collection • Instances from different services cannot access the same collection Reliable Collection – visibility
- 34.
- 35.
- 36. @ITCAMPRO Timers and Reminders Timers Similarwith .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: Multiplecalls to the same Reliable Actor Concurrency
- 38.
- 39.
- 40. @ITCAMPRO Execution flow: • ReminderTrigger • SetPrice • SetStock Concurrency
- 41.
- 42. @ITCAMPRO Events • Send eventsand 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.
- 45.
- 46.
- 47.
- 48. @ITCAMPRO Fault Domains andUpgrade Domains
- 49. @ITCAMPRO Where we cancontrol them Application • Partitioning • Replication Cluster • Fault Domain • Upgrade Domain • Naming Service • Resource Balancer • Failover Manager
- 50.
- 51.
- 52. @ITCAMPRO { “name” : “RaduVunvulea, “blog” : “vunvulearadu.blogspot.com”, “email” : ”vunvulear@outlook.com”, “socialMedia” : { “twitter” : “@RaduVunvulea”, “fb” : “radu.vunvulea” } }