Practical design patterns in the age of the cloud
summary
Argues monitoring and diagnostics are mandatory: enable Azure Monitor, turn on per-service diagnostics, tag resources, assign a budget owner, and use alerts wired to webhooks or paging. Gives a real abuse case — an API user sent ~300,000 emails — and prescribes a throttle pattern or API Management gateway plus ability to switch off abusers. Recommends storage tactics: materialized views or CQRS to avoid cross-region DB sync, Azure SQL geo‑replication or Cosmos DB multi‑master, and the valet key (SAS) + 302 redirect plus Event Grid → Azure Functions to upload/download files without shuffling bits through app servers.
AI-written summary · about
chapters (10)
- 0:00Introduction to Azure
- 4:28Practical Azure Design
- 8:36Importance of Monitoring
- 16:13Throttling and APIs
- 21:22Storage Patterns
- 26:31CQRS and Database Design
- 29:52Valet Key Pattern
- 36:43Cloud Design Principles
- 40:53Resiliency in the Cloud
- 45:51Q&A and Summary
related talks
47m8 Cloud Design Patterns you ought to know.
35mCloud Patterns
01h 00mMonitoring a Global Multitenant Service
27mDesigning Secure Applications in the Cloud
34mDesigning Secure Applications in the Cloud
43mDesigning software in the cloud
49mMonitoring real-life Azure applications: When to use what and why
38mLogging, Instrumentation, Dashboards, Alerts