Chapter Seven

Developer Tools & Integration

Seven services for shipping code and decoupling systems — pipelines and a container registry on the delivery side, messaging and eventing on the integration side. Choosing the wrong messaging primitive is a costly rewrite.

7 services

Core Terminology

Delivery and integration on Azure share a vocabulary for pipelines and messaging. These terms recur across the chapter.

Pipeline
An automated build-test-deploy workflow defined as YAML in Azure Pipelines, triggered by commits and gated by approvals.
Message vs Event
A message is a command with an expectation (Service Bus); an event is a notification of something that happened (Event Grid). The distinction drives the service choice.
Topic & Subscription
A publish-subscribe pattern where publishers send to a topic and multiple subscribers receive filtered copies — in both Service Bus and Event Grid.
Throughput Unit
Event Hubs' capacity dial for ingress and egress. Streaming millions of events per second means provisioning or autoscaling these.
Dead-Letter Queue
A holding queue for messages that cannot be delivered or processed, so failures are captured rather than lost.
Stateful Workflow
A long-running orchestration, as in Logic Apps, that waits on external events and survives restarts without you managing the state.

Services in This Chapter