How do I decouple producers and consumers with pub/sub?

To decouple producers and consumers with pub/sub (publish/subscribe), you insert a broker or event bus between them so they no longer call each other directly.

Core idea

• Producers only publish messages/events to a topic/channel.
• Consumers subscribe to topics they care about.
• The broker delivers messages to all matching subscribers.

This gives you:

• Loose coupling: producers don’t know who consumes.
• Independent scaling: producers and consumers can scale separately.
• Flexibility: add/remove consumers without changing producers.

Typical flow

1. Producer creates an event, e.g. OrderCreated.
2. Producer sends it to a topic, e.g. orders.
3. Broker stores/routes it.
4. Any consumer subscribed to orders receives it.
5. Each consumer processes it independently.

What this decouples

1. Time decoupling

Producer and consumer do not need to be online at the same time, if the broker persists messages.

2. Location decoupling

Producer does not need to know where consumers are running.

3. Implementation decoupling

Producer does not care how many consumers exist or what they do with the event.

Design tips

• Publish events, not direct commands, when you want loose coupling.
• Use topic names that reflect business concepts.
• Keep messages self-contained so consumers don’t need to call back the producer.
• Make consumers idempotent in case messages are delivered more than once.
• Decide whether you need:
  • fan-out: every subscriber gets the message
  • competing consumers: one of many workers handles each message

Example

A shopping app:

• CheckoutService publishes OrderPlaced
• EmailService subscribes and sends confirmation email
• InventoryService subscribes and reserves stock
• AnalyticsService subscribes and records metrics

CheckoutService doesn’t know about any of them.

Common technologies

• Kafka
• RabbitMQ
• SNS/SQS
• Google Pub/Sub
• NATS
• Redis Pub/Sub
• MQTT

Simple mental model

Think of it like a radio station:

• The station broadcasts on a frequency.
• Listeners tune in if they want that content.
• The station doesn’t know who is listening.

If you want, I can also show:

1. a diagram,
2. a code example in your language, or
3. the difference between pub/sub and message queues.