non_functional_requirements

dz / system_design_interview / toc / 04_distributed_message_queue / step1 / non_functional_requirements

Node Tree

• high_throughput_or_low_latency
• persistent_durable
• scalable

Nodes

high_throughput_or_low_latency
content	High Throughput or Low Latency, configurable based on use cases
parents	system_design_interview/toc/04_distributed_message_queue/step1/non_functional_requirements
location	knowledge/system_design_interview.dz:73

scalable
content	Scalable: the system should be distributed. Should be able to support a sudden surge in message volume.
parents	system_design_interview/toc/04_distributed_message_queue/step1/non_functional_requirements
location	knowledge/system_design_interview.dz:78

persistent_durable
content	Persistant and durable: data should be persisted on disk and replicated across multiple nodes
parents	system_design_interview/toc/04_distributed_message_queue/step1/non_functional_requirements
location	knowledge/system_design_interview.dz:84