This document discusses microservices on Azure. It provides an overview of microservice patterns including the benefits of microservices like increased autonomy, scalability and team allocation. It also discusses challenges like discoverability. The document introduces Azure Service Fabric for building microservices and related cloud patterns like proxy, shared data and load leveling microservice patterns. It recommends microservices for highly skilled developers working on complex projects.

1. MicroServices on Azure
Tech-Talks | Team Technologies LLC
Sergey Seletsky
Senior Solutions Architect

2. Agenda
 Evolution of Architecture
 MicroService Pattern
 MicroService Challenges
 MicroService Benefits
 Azure Service Fabric
 Related Cloud Patterns
 Conclusions

3. Evolution of Architecture
Desktop
Client
Server
Browser
Web Server
Db Server
Any Device
microservices
API Proxy

4. Evolution of Architecture

5. MicroService Pattern
MicroService Architecture Style

6. Team Work Allocations problem
 Conflicts in source control
 Mixed domains
 Technology constraints
 Blocking issues
 IDE Overload
 Slow builds
 Slow tests

7. Monolithic Architecture
 Services was too complex
 Hard to support
 Hard to deploy
 Hard to scale

8. MicroService Pattern
 Single Responsible
 Domain Driven
 Isolated
 Independently hosted
 Autonomous
 Elastic
 Programmable
 Discoverable
 Automated

9. Team Work Allocations with MicroServices
Team A
• Authorization
• C#
• Service Fabric
Team B
• Customers
• Java
• Amazon EC2
Team C
• Orders
• JavaScript
• AWS Lambda
• You can allocate feature per team and parallelize development without overhead.
• Recommended to use one technology per solution, but it is possible to use one per team.
• Recommended to use one hosting platform per solution, but it is possible to use more.

10. MicroService Logical Architecture
•Angular UI and CordovaExperience
•NPM Packaged SDKSDK
•REST/HTTPProtocol
•On the wire data modelsModels
•Node.JsService
•Express Mongo ClientDAC
•Mongo DbStore
•Continuous DeliveryAutomation
•Xamarin / WPFExperience
•NuGet Packaged SDKSDK
•REST/HTTPProtocol
•Data ContractsModels
•.NET Core Web APIService
•Document Db ClientDAC
•Document DbStore
•Continuous DeliveryAutomation
Example 1 - JS Example 2 – C#

11. MicroService Challenges
MicroService Architecture Challenges

12. Warning! Only for Highly Skilled Developers!

13. MicroService Challenges

14. Discoverability

15. MicroService Benefits
MicroService Architecture Benefits

16. MicroService Benefits

17. Density & Isolation levels
PC VM ProcessContainer
More isolated More efficient
Hardware Not shared Shared Shared Shared
Kernel Not shared Not shared Shared* Shared
System Resources
(ex: File System)
Not shared Not shared Not shared Shared

18. Lower costs for complex projects

19. The Scale Cube and MicroServices

20. Full power of Clouds

21. Azure Service Fabric
MicroService Architecture powered by Azure

22. Azure Service Fabric

23. Azure Service Fabric

24. Azure Service Fabric

25. Examples

26. Examples

27. Related Cloud Patterns
MicroService Architecture Cloud Patterns

28. Proxy MicroService Design Pattern

29. Shared Data MicroService Design Pattern

30. Load Leveling Design Pattern

31. Federated Identity Pattern

32. Retry Pattern

33. Sharding Pattern

34. Reading
Domain Driven Design
Eric Evans
Continuous Delivery
Jez Humble
David Farley
Azure Service Fabric
Haishi Bai
Building Microservices
Sam Newman