Requirements of a Distributed Messaging Queue’s Design

Define the messaging contract first: when a message is accepted, how it becomes visible, and what a consumer acknowledges. A single-server baseline helps identify which guarantees require replication or distributed ownership.

Requirements

A distributed messaging queue stores data across multiple machines. The design must satisfy the following functional and non-functional requirements.

Functional requirements

Clients must be able to perform the following actions:

• Queue creation: Clients create a queue and define parameters such as the queue name, queue size, and maximum message size.

• Send message: Producers send messages to a designated queue.

• Receive message: Consumers retrieve messages from their designated queues.

• Delete message: Consumers delete a message from the queue after successfully processing it.

• Queue deletion: Clients delete a specific queue.

Non-functional requirements

Make the nonfunctional requirements testable: