The move away from the traditional model of hosting our tiered applications on VMs to a more Serverless/Cloud Native posture means less admin overhead when it comes to maintaining the underlying Infra and we just need to pick the correct SKU and set up scaling ….

Or does it? Scaling isn't linear across all Azure PAAS Services, so we need to ensure that we have the correct SKU's and baselines defined for each of those services based on the expected load.

In this session, I'll look at how scaling times can differ across services, getting those auto-scaling rules right, and how Azure Load Testing can help set that baseline.

- Overview of standard Azure PAAS Services and what they do
- Example of an application using multiple PAAS Services
- How these services scale? Auto Scaling?
- Can the services scale in time to keep your application alive?
- How can you know if you have the correct SKU
- Overview of Azure Load Testing
○ JMeter Files
○ Test Engines
§ Client Metrics
○ Load
○ Parameters
○ Criteria
○ Pricing
§ Virtual User Hours
○ RBAC Roles
- Azure Load Test
○ Dashboards
○ Endpoints
§ Server Metrics
□ Goes to Azure Monitor
○ Identifying Bottlenecks
○ Automate Load tests using CI/CD with Azure DevOps
○ Integrate with Azure Key Vault