3 - DevOps in a Cloud World
In this first-guest episode of Cloud with Chris, Abel Wang — Principal Developer Advocate and DevOps Lead at Microsoft — joins Chris Reddington for a wide-ranging conversation on what DevOps really means and how to put it into practice in a cloud-first world.
Key topics covered in this episode:
- Defining DevOps — Microsoft’s framing of DevOps as the union of people, process, and products focused on continuously delivering value to end users, not just shipping features
- Telemetry and data-driven decisions — how telemetry revealed that only one-third of features built at Microsoft actually delivered the value users wanted (one-third were neutral and one-third were actively unwanted), and how measuring actual usage changed the team’s development approach
- Feature flags — separating deployment from release, enabling safe experimentation with subsets of users, supporting rapid rollback, and keeping flag debt under control
- Database DevOps — storing database schemas in source control, automating schema migrations, and breaking the traditional DBA bottleneck to support high-frequency deployments
- Site Reliability Engineering (SRE) — embedding on-call responsibility directly in cross-functional product teams, using live-site incidents as the fastest way to ramp up new engineers
- Shifting left — moving quality, security, and reliability considerations earlier in the delivery pipeline to reduce the cost of fixing defects in production
If you are earlier in your DevOps journey or looking to level up specific practices like CI/CD pipelines, feature flags, or database automation, this episode is packed with practical insights drawn from real experience inside Microsoft engineering teams.
Related Content
2 - Cost Control
Moving to the cloud shifts infrastructure spend from capital expenditure (CapEx) to operational expenditure (OpEx)—but only if you think about cost correctly from the start. This episode covers the cloud cost mindset: right-sizing, auto-scaling (scale out vs scale up), compute resource consolidation, governance through resource tagging and policy, pricing calculators, reserved instances, and how to build cost awareness into your architecture from day one.
1 - Requirements in Context
Every cloud project starts with requirements. In this episode, Chris explores the critical pillars of cloud architecture: resilience (SLA, RTO, RPO, MTTR, MTBF), scalability, performance, and cost. Learn why defining requirements upfront—before drawing architecture diagrams—is essential, and how the same on-premises thinking about availability translates directly into the cloud.
There are no clear architecture patterns for the Cloud? (Azure Mythbusters)
Cloud design patterns are abundant and well-documented on the Azure Architecture Center — from established patterns like cache-aside and materialized view to cloud-native ones like circuit breaker and health endpoint monitoring. This Azure Mythbusters episode tours the full pattern catalogue and deep-dives four key patterns: cache-aside, circuit breaker (open/half-open/closed states), health endpoint monitoring, and materialized view in CQRS/event sourcing scenarios.