Step 1: Requirements
Requirements
Questions to ask
- In-process or distributed (separate broker process)?
- At-most-once, at-least-once, or exactly-once delivery?
- Need persistent messages (survive broker restart)?
- Message ordering guarantees?
- Dead letter queue for failed messages?
- Topic-based or content-based routing?
- 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