7
Back to Problem Dungeon

Pub-Sub Message Broker

medium

Step 1: Requirements

Requirements

Questions to ask

  1. In-process or distributed (separate broker process)?
  2. At-most-once, at-least-once, or exactly-once delivery?
  3. Need persistent messages (survive broker restart)?
  4. Message ordering guarantees?
  5. Dead letter queue for failed messages?
  6. Topic-based or content-based routing?
  7. Need consumer groups (load balancing across subscribers)?

Functional requirements

  • Publishers send messages to named topics
  • Subscribers register for topics and receive matching messages
  • Support multiple subscribers per topic (fan-out)
  • Messages are delivered asynchronously
  • Dead letter queue for messages that fail processing N times
  • Unsubscribe support

Non-functional requirements

  • At-least-once delivery (subscriber must ack)
  • Topic creation on first publish (lazy)
  • Extensible to distributed system (but start in-process)
  • Observable: message count per topic, subscriber lag

1 / 7 — Requirements