Instiq
Chapter 4 · Design Infrastructure Solutions·v2.0.0·Updated 6/3/2026·~11 min

What's changed: Deepened AZ-305 Chapter 4 (added comparison tables, scenarios, FAQs, exam traps, deep-dive paragraphs to each section; localized figures to Japanese)

4.2Designing App Integration and Messaging

Key points

Understand loosely coupled integration—Service Bus/Event Grid/Event Hubs, API Management, Logic Apps, and Azure Cache for Redis. Decouple components and integrate at scale.

Scalable design starts with loose coupling. Choose among Service Bus, Event Grid, and Event Hubs by purpose.

4.2.1Messaging and integration

Diagram of Azure messaging/integration by purpose: enterprise messaging (ordering/transactions/dead-letter) = Service Bus (queues/topics); reactive event delivery (pub/sub, state-change notifications) = Event Grid; high-volume streaming ingestion of big data/telemetry = Event Hubs; gateway for published APIs (auth/throttling/versioning) = API Management; no-code workflow integration = Logic Apps; low-latency caching = Azure Cache for Redis.
Messaging and integration
  • Service Bus: enterprise messaging (queues/topics; ordering/transactions/dead-letter).
  • Event Grid: reactive event delivery (pub/sub, state-change notifications).
  • Event Hubs: high-volume streaming ingestion (telemetry/big data).
  • API Management/Logic Apps/Redis: API gateway / no-code integration / low-latency cache.
Exam point

Common on AZ-305: ordered/transactional enterprise messaging = Service Bus, state-change event notifications = Event Grid, high-volume telemetry stream = Event Hubs, API publishing gateway = API Management, no-code workflows = Logic Apps. Distinguishing the three messaging services is key.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.