Comparison questionEasy~5 minMessaging & Event-Driven Essentials / 2 of 16

Interview question

How would you explain the difference between a queue and a topic?

Compare queues and topics for backend messaging

Compares point-to-point queues with publish-subscribe topics and explains when each model fits.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

A queue is usually point-to-point work distribution: one message is processed by one consumer instance from a consumer group. It is useful for jobs like sending an email or processing an export. A topic is publish-subscribe: one event can be delivered to multiple independent subscriptions. It is useful when several parts of the system need to react to the same business event.

Full answer below

Practice focus

Point-to-point work distribution, publish-subscribe, fan-out, consumer independence, and delivery semantics.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
A queue distributes one logical unit of work to one consumer, while a topic delivers one published fact to independent subscriptions. The choice determines ownership, fan-out, scaling, and contract responsibilities.
A queue is usually point-to-point work distribution: one message is processed by one consumer instance from a consumer group. It is useful for jobs like sending an email or processing an export. A topic is publish-subscribe: one event can be delivered to multiple independent subscriptions. It is useful when several parts of the system need to react to the same business event.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would choose based on ownership. If one service owns the work and scaling means adding more workers, a queue is a good fit. If an order placed event needs billing, notifications, analytics, and fulfillment to react independently, a topic is cleaner. Topics introduce more contract responsibility because every subscriber depends on the event schema and timing. Queues are simpler when there is only one logical owner of the work.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production each topic subscriber owns an independent subscription, retry budget, dead-letter path, and deployment lifecycle so one broken consumer cannot block the others. Events use stable business meaning and backward-compatible schemas rather than exposing the publisher's internal model. Retention and replay policy are explicit because a new or repaired subscriber may need historical events. The producer publishes through an outbox when the event must agree with committed state, while consumers remain idempotent because subscription delivery can repeat.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Using a topic when there is only one logical consumer.
Using one shared subscription for unrelated consumers.
Publishing internal database-shaped events as public contracts.
Ignoring subscriber failure and dead-letter handling.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot explain fan-out.
Thinks a topic automatically means many workers share one job.
Ignores event schema compatibility.
Has no answer for one subscriber being down.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

When would each subscriber need its own subscription?
What makes an event a good public contract?
How would you add a new subscriber safely?

Continue the section

Next in Messaging & Event-Driven Essentials: Commands vs Events

Step 3 of 16

Distinguish commands and events in message-driven systems

Opening drill

Comparison questionEasy~5 minMessaging & Event-Driven Essentials / 2 of 16

Interview question

How would you explain the difference between a queue and a topic?

Compare queues and topics for backend messaging

Compares point-to-point queues with publish-subscribe topics and explains when each model fits.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Point-to-point work distribution, publish-subscribe, fan-out, consumer independence, and delivery semantics.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
A queue distributes one logical unit of work to one consumer, while a topic delivers one published fact to independent subscriptions. The choice determines ownership, fan-out, scaling, and contract responsibilities.
A queue is usually point-to-point work distribution: one message is processed by one consumer instance from a consumer group. It is useful for jobs like sending an email or processing an export. A topic is publish-subscribe: one event can be delivered to multiple independent subscriptions. It is useful when several parts of the system need to react to the same business event.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would choose based on ownership. If one service owns the work and scaling means adding more workers, a queue is a good fit. If an order placed event needs billing, notifications, analytics, and fulfillment to react independently, a topic is cleaner. Topics introduce more contract responsibility because every subscriber depends on the event schema and timing. Queues are simpler when there is only one logical owner of the work.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production each topic subscriber owns an independent subscription, retry budget, dead-letter path, and deployment lifecycle so one broken consumer cannot block the others. Events use stable business meaning and backward-compatible schemas rather than exposing the publisher's internal model. Retention and replay policy are explicit because a new or repaired subscriber may need historical events. The producer publishes through an outbox when the event must agree with committed state, while consumers remain idempotent because subscription delivery can repeat.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Using a topic when there is only one logical consumer.
Using one shared subscription for unrelated consumers.
Publishing internal database-shaped events as public contracts.
Ignoring subscriber failure and dead-letter handling.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot explain fan-out.
Thinks a topic automatically means many workers share one job.
Ignores event schema compatibility.
Has no answer for one subscriber being down.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

When would each subscriber need its own subscription?
What makes an event a good public contract?
How would you add a new subscriber safely?

Continue the section

Next in Messaging & Event-Driven Essentials: Commands vs Events

Step 3 of 16

Distinguish commands and events in message-driven systems

How would you explain the difference between a queue and a topic?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

How would you explain the difference between a queue and a topic?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section