9 - Building smart Integration Solutions with Microsoft Azure
When we think about cloud architecture, we typically think about distributed systems and the challenge of bringing different components or services together. But integration in the cloud is more nuanced than simply connecting services — it requires understanding messaging semantics, failure modes, and observability.
In this episode, Chris is joined by Ezhilarasi Chezhiyan, Technical Lead at Serverless360 (Kovai.co), to explore practical patterns for building smart Azure integration solutions.
Events vs. Messages — a critical distinction
One of the most common sources of confusion is the difference between an event and a message. An event is a notification that something happened — lightweight, with no expectation of a response. A message is a command or data payload that expects a receiver to act on it. Choosing the wrong tool based on this misunderstanding leads to brittle integrations.
Azure messaging services compared
- Azure Service Bus — Full-featured message broker with FIFO ordering, dead letter queues, duplicate detection, and sessions. Ideal for reliable command/response workflows.
- Azure Event Grid — Event routing service based on a publish-subscribe model. Best for reacting to state changes across Azure services and custom topics.
- Azure Event Hubs — High-throughput event streaming platform designed for telemetry ingestion and stream processing at scale.
Cloud design patterns in practice
The episode covers how patterns like queue-based load leveling, competing consumers (fan-out via Service Bus topics and subscriptions), dead letter queues, retry policies, and circuit breakers apply to Azure serverless workloads.
Observability gap for business monitoring
Ezhilarasi explains the limitations of Azure Monitor, Log Analytics, and Application Insights for business-level monitoring of integration flows — particularly for non-technical stakeholders. Serverless360 fills this gap with composite application mapping and end-to-end business activity monitoring across Logic Apps, Functions, and Service Bus.
Related Content
5 - The API Economy
APIs are the connective tissue of modern cloud architectures — but poor API design compounds into technical debt that is expensive to unwind. In this episode, Chris Reddington and Peter Piper explore the full lifecycle of API design: defining versioning contracts up front, modernising legacy APIs using the Strangler and Façade patterns, and securing APIs with JWT tokens, OAuth 2.0, and OIDC. They also cover Azure API Management patterns, circuit breakers, throttling, key rotation with Azure Key Vault, and the DevSecOps practices that keep an API estate healthy at scale.
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.
8 - Azure Security
Moving to Azure? Security has to come first. Chris is joined by cybersecurity expert Andrew Nathan to explore how organisations can build a strong security posture in the cloud — covering Azure Security Center and Secure Score, identity strategy (Azure AD vs. Azure RBAC), multi-factor authentication, threat modelling, Azure Policy and Management Groups for governance, and the evolution of security operations into red team/blue team war gaming. Whether you're starting your cloud journey or course-correcting an existing environment, this episode will help you understand where to begin and how to keep improving over time.