# A Single Subscriber Doesn't Turn Pub/Sub Into a Queue

DevFeed: [A Single Subscriber Doesn't Turn Pub/Sub Into a Queue](<https://devfeed.tech/articles/a-single-subscriber-doesn-t-turn-pub-sub-into-a-queue-17947.md>)

Original publisher: [Read original article](<https://newsletter.systemdesignclassroom.com/p/a-single-subscriber-doesnt-turn-pubsub-into-a-queue>)

Author: Raul Junco

Published: 2026-02-28T12:52:05Z

Content type: tutorial

Language: en

Sources: [System Design Classroom](<https://devfeed.tech/sources/system-design-classroom.md>)

Topics: [systems](<https://devfeed.tech/topics/systems.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [async](<https://devfeed.tech/tags/async.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [pdf](<https://devfeed.tech/tags/pdf.md>), [queue](<https://devfeed.tech/tags/queue.md>), [retry](<https://devfeed.tech/tags/retry.md>), [systems](<https://devfeed.tech/tags/systems.md>)

## AI overview

The article explains that asynchronous system patterns should be classified by execution semantics rather than by the messaging technology used. A report-generation flow with one worker processing each job, retries after failure, and additional workers sharing increased demand is a work queue, not pub/sub.

## Source excerpt

Why execution semantics -not tooling- define async patterns.