So you’ve decided you are ready to embrace microservices? Now begins another fun part of your journey - choosing the platform that fits your team, your solution, and your technology choices. Up to a point the microservices platform is irrelevant during the design phase, but at some you need to align the design with a platform. On Azure you have many choices including Docker, Windows Containers, Azure Container Service and Service Fabric. Come to this session for a peak at the capabilities and approaches for each; and insights on how to select the platform that fits best for your next green field solution or migration to microservices.

1. Microservices on Azure
choosing the right approach
for your solution
Michele Leroux Bustamante
Cofounder / CIO Solliance
Cloud/Security Architect
michelebusta@solliance.net

2. Remember
HELLO WORLD
1992?

3. Hello
World!

5. HELLO WORLD
Today…something like this…

6. iPhoneWindows
Phone
Surface
WPF / Rich
Client
Android
iPad
Web API Web App
Mobile
Browsers
Services

7. © Michele Leroux Bustamante. All rights reserved.
How did we get here?
 Monolithic apps
 Client / server apps
 Distributed components
 Service-Oriented Architecture (SOA)
 Cloud-enabled solutions / PaaS
 Microservices architecture

8. 8
• Discrete
• Atomic
• Independently
deployable
• Bounded context
• Fit in your head

9. iPhoneWindows
Phone
Surface
WPF / Rich
Client
Android
iPad
Mobile
Browsers

10. © Michele Leroux Bustamante. All rights reserved.
Microservices Build on SOA
 Loose coupling
 reusable
 encapsulated and autonomous
 Separation of concerns
 platform / technology independent
 discoverable (registry services)
 Service Oriented
 well-defined contracts
 composable (alone or with other services)
 High cohesion
 Shared nothing
architecture
 Context Mapping
 Full stack, dynamic
deployment
 Parallel, non-blocking
development

11. © Michele Leroux Bustamante. All rights reserved.
Design

12. Design is Technology Independent
should be
starts out

13. © Michele Leroux Bustamante. All rights reserved.
Breaking Down Services
Mobile
Admin
Internal
Web
Recommendations
Service
Identity
Service
Users /
Profile
Account
Info
User
Permissions
Cache
Account
Service
Permissions
Service
ShoppingCart
Service
Customers
Service
Customers
Email
Service
Fulfillment
Fulfillment
Service
Orders
Service
Orders
Machine
Learning /
Analytics
Payment
Payment
Service
Product
Product
Service

14. Containerization

15. Virtualization vs. Containerization
VM
OS
Docker Engine
VM
Host OS
Hypervisor
Guest OS Guest OS Guest OS
Binaries Binaries Binaries
App A App B App B
Binaries Shared Binaries
App A App B App B
Container
NOT
a Container

16. Virtualization vs. Containerization
VM
OS
Docker Engine
VM
Host OS
Hypervisor
Guest OS Guest OS Guest OS
Binaries Binaries Binaries
App A App B App B
Binaries Shared Binaries
App A App B App B
No OS
OS
Fast
Efficient
Simple
Practical

18. DEMO

19. ### Dockerfile for Windows
FROM windowsservercore
RUN dism /online /enable-feature /all /featurename:iis-webserver /NoRestart
RUN echo "Hello World - Dockerfile" > c:inetpubwwwrootindex.html
### build the image and run
docker build -t iis .
docker run --name iisdemo -it -p 80:80 iis cmd

20. © Michele Leroux Bustamante. All rights reserved.
Windows or Hyper-V Containers?
 Hyper-V protects the kernel
 Not available on Azure today

21. © Michele Leroux Bustamante. All rights reserved.
Windows Containers
 Containers on Windows Server?
 Windows Server 2016 Tech Preview 4
 Distribution of docker engine for windows
 Support for docker-cli or powershell commands
 The Docker daemon for Windows Server does not run Linux images!
 Create images based on windowsservercore
 What can you put into the image?
 Anything that runs on windows
 What about tools?
 We have Docker Engine, Docker Swarm, Docker Networking
 However…things don’t quite work the same (yet)

22. © Michele Leroux Bustamante. All rights reserved.
Scheduling and Discovery Demo
 How should services be deployed?
 1 per box, poor mans devops ok
 Density, best use of resources, need a scheduler
 Concepts
 Schedule deployments via master node cluster
 Tracks live containers via registration
 Tracks available resources via agent

23. © Michele Leroux Bustamante. All rights reserved.
Docker / Swarm

24. © Michele Leroux Bustamante. All rights reserved.
Mesos / Marathon

25. © Michele Leroux Bustamante. All rights reserved.
Azure Container Service
 Parameterized ARM templates that initialize your cluster
 Swarm / Mesos

26. © Michele Leroux Bustamante. All rights reserved.
Why you need more than just docker
 Geographic load balancing
 Fail fast service interactions (circuit breakers)
 Auto-scalability and service resiliency
 Centralized logging of operational and business activity
 Automated deployment
 Lightweight infrastructure
 Update deployment strategy (immutable or pushed artifact update)

27. Virtual Network
Subnet1
Front End
Stateless
Web / API
Services
HTTP/S
80/443
Back End
Stateless
Compute`
Stateful
Compute
Azure
Service
Fabric

29. © Michele Leroux Bustamante. All rights reserved.
Migration Roadmap
 Re-think Architecture Patterns and Principles
 Re-shape Team Collaboration Practices
 Re-invent the Platform
 Re-factor the Monolith

30. Without automation the explosion of moving
parts would be infinitely challenging

31. © Michele Leroux Bustamante. All rights reserved.
Finding the Right Fit
Skills
Effort
Cost
Timeline
Momentum
Culture
Microservices
Design
Requirements
Platform
Choices
Considered

32. © Michele Leroux Bustamante. All rights reserved.
About Michele
 Michele Leroux Bustamante
 michelebusta@solliance.net
 @michelebusta
 Solliance Cofounder
 Cloud / Security Architect
 Microsoft Regional Director since 2003
 Microsoft MVP – Microsoft Azure
 Azure Elite, Azure Insider