System V message queues predate and directly inspired the message-type-and-priority model that production brokers like RabbitMQ and ZeroMQ still expose today, letting unrelated processes exchange structured, typed messages without the strict FIFO-only constraint of a pipe. The kernel persistence this task highlights is a double-edged sword in practice: forgotten message queues from crashed test programs are a classic source of `/proc/sys/kernel/msgmni` exhaustion on long-running Linux servers, which is exactly why `ipcs`/`ipcrm` exist.