section.io - Expanding from AWS to Azure
- 1. section.io Expanding from AWS to Azure
- 2. section.io AWS infrastructure simplified Browsers Load Balancer Proxy Container Host Origin Web Servers DNS-based Routing Management Portal Log Indexing Configuration Database API
- 3. Why Azure? • Location, location, location • AWS is not infallible • Platform agnostic
- 4. What did we provision in Azure? • Linux virtual machines • Load balancers • DNS routing Load Balancer Proxy Container Host DNS-based Routing
- 5. Translation AWS Azure EC2 Instance Virtual Machine Elastic Load Balancer Load Balancer Auto Scaling Group Virtual Machine Scaling Set* CloudFormation Resource Manager Template Route53 Latency Routing Policy Traffic Manager
- 6. Azure load balancers are awesome • PROXY protocol not required • Direct Server Return • UDP support
- 7. Also awesome on Azure • Resource Manager Templates • Compare actual state • SecureString parameters • Multi-location • Resource Explorer • https://resources.azure.com • Price
- 8. Where Azure is different • Azure Availability Sets • Less tangible • Cross-Zone Load Balancing • Subnets
- 9. Where Azure is surprisingly different • Virtual Machines Scale Sets • Cannot be created in the portal* • Virtual Machines can’t receive public IP addresses • Virtual Machine identification
- 10. Suboptimal in Azure • Documentation • Load Balancer separation-of-concerns • Virtual Machine Scale Set “CustomData” property • Resource Template encoding
- 11. Pending tasks for our Azure deployment • Machine Images • Resource Naming • Log Shipping • Load Balancer Diagnostics
- 12. Thank you • Jason Stangroome • jason@section.io • @jstangroome • https://section.io