Latest posts
-
Part 5 of 5: Azure Production Readiness Review — SLOs, Alerts, Backups and Recovery
Azure DevOps & Monitoring series — Part 5 of 5. A production readiness review checks whether an Azure workload can be operated and recovered, not just whether it deploys successfully.
-
Part 4 of 5: Application Insights Distributed Tracing — Follow Requests Across Services
Azure DevOps & Monitoring series — Part 4 of 5. Distributed tracing connects requests and dependencies across multiple services using operation and trace context. It helps engineers find where latency or failure occurs in a multi-service application.
-
Part 3 of 5: Azure DevOps Environments and Approvals — Control Production Releases
Azure DevOps & Monitoring series — Part 3 of 5. Azure DevOps environments provide deployment history and support checks and approvals for controlled releases. They help teams separate deployment permissions from source-code permissions.
-
Part 2 of 5: Azure Bicep Modules — Reuse Infrastructure Definitions Safely
Azure DevOps & Monitoring series — Part 2 of 5. Bicep modules split infrastructure into reusable components. They help teams standardize resource configuration and avoid copying large templates between projects.
-
Part 1 of 5: Azure DevOps YAML Pipelines — Build a Multi-Stage CI/CD Workflow
Azure DevOps & Monitoring series — Part 1 of 5. YAML pipelines define build and deployment steps as code. Multi-stage pipelines separate validation, packaging and environment promotion so teams can review changes and apply approvals consistently.
-
Part 5 of 5: Azure Cosmos DB Consistency Levels — Choose the Right Read Behaviour
Azure Storage & Data Services series — Part 5 of 5. Cosmos DB consistency levels trade read guarantees against latency and availability. The appropriate choice depends on the application’s correctness needs and the configured account and client behaviour.
-
Part 4 of 5: Azure SQL Database Connection Pooling — Prevent Connection Exhaustion
Azure Storage & Data Services series — Part 4 of 5. Connection pooling reuses physical database connections across logical opens. Poor connection lifetime management or excessive parallelism can exhaust available connections and cause cascading failures.
-
Part 3 of 5: Azure Queue Storage — Design Idempotent Background Workers
Azure Storage & Data Services series — Part 3 of 5. Queue Storage decouples producers from background workers. Messages can be delivered again, so consumers should be idempotent and should handle visibility timeouts and poison messages.
-
Part 2 of 5: Azure Blob Uploads with .NET — Stream Large Files Safely
Azure Storage & Data Services series — Part 2 of 5. Streaming uploads avoid loading an entire large file into application memory. The Azure Storage SDK supports upload APIs that work with streams and can manage block uploads.
-
Part 1 of 5: Azure Blob Storage Containers and Access Tiers — Organize Object Data
Azure Storage & Data Services series — Part 1 of 5. Blob Storage containers organize object data, while access tiers help align storage cost with access frequency. The data layout should reflect security boundaries, retention and retrieval patterns.