system_design_interview/toc/04_distributed_message_queue/step1/functional_requirements

functional_requirements

dz / system_design_interview / toc / 04_distributed_message_queue / step1 / functional_requirements

Node Tree

Nodes

producers_send_messages
content Producers send messages to a message queue
children consumers_consume_messges
parents system_design_interview/toc/04_distributed_message_queue/step1/functional_requirements
location knowledge/system_design_interview.dz:32

consumers_consume_messges
content Consumers consume messages from message queue
parents system_design_interview/toc/04_distributed_message_queue/step1/functional_requirements, producers_send_messages
location knowledge/system_design_interview.dz:36

messages_consumed_repeatedly_or_once
content messages can be consumed repeatedly or only once
children delivery_semantics_configurable
parents system_design_interview/toc/04_distributed_message_queue/step1/functional_requirements
location knowledge/system_design_interview.dz:41

message_size_kb_range
content Message size in kilobyte range
parents system_design_interview/toc/04_distributed_message_queue/step1/functional_requirements
location knowledge/system_design_interview.dz:45

deliver_in_order
content Ability to deliver messages to consumers in the order they were added to the queue
parents system_design_interview/toc/04_distributed_message_queue/step1/functional_requirements
location knowledge/system_design_interview.dz:49

delivery_semantics_configurable
content Data delivery semantics (at once, at most-once, or exactly once) can be configured by users
parents messages_consumed_repeatedly_or_once, system_design_interview/toc/04_distributed_message_queue/step1/functional_requirements
location knowledge/system_design_interview.dz:54

history_can_be_truncated
content Historical data can be truncated
parents system_design_interview/toc/04_distributed_message_queue/step1/functional_requirements
location knowledge/system_design_interview.dz:60