Message queue permanently holds messages from a sender until the intended receiver is ready to read them.

When a message queue is first created, the FSM is in the full state

Message queue usually either a FIFO or priority-based order

Message queue state only consist of two states : empty and not empty

If the number of messages in the queue is equal to the queue's length, it means the message queue's state becomes full

Message queue need one copy mechanism when deliver message from sender task to receiver task

Message queue can be used to send temperature value from a sensor

System pool requires enough reserved memory area for the full capacity of every message queue that will be created.

In a destructive read, when a task successfully receives a message from a queue, the task permanently removes the message from the message queue’s storage buffer