A topic names a publication path, while a subscription holds an independent delivery relationship for its consumer. Copper Returns needs both ledger and audit to receive the same event. Two workers sharing one subscription are not the same design as two independent subscriptions.
Match the delivery relationship to the business need before tuning a worker. Retention and acknowledgment deadlines describe different boundaries, and a published event does not mean each downstream operation has completed. The local adapter delivers copies into its existing subscription records and tracks acknowledgments. It does not run a distributed broker, enforce retention expiry, evaluate IAM or manage real consumer throughput. These tasks create local topics and subscriptions, then examine which consumer sees which work. All payloads and references are original fictional training data.
Choose independent subscriptions when every consumer needs every event.