Design a MySQL table for message queue to store message data

1.  Queue attribute table

Record the properties of all message queues that have been created . This table applies to point-to-point messages , That is, after a message is created by the producer , Can only be consumed by one consumer . In case of subscription mode , The queue type should be added to this table （ Point to point queues 、 Subscription queue ）

1.  Table structure description

Each message queue corresponds to a table , When creating a message queue , At the same time, create a table for the message queue , Here's why ：

• Reduce the interaction between different message queues , Reduce the performance requirements of single meter ;

• Reduce the total number of messages in a single table , Improve query efficiency ;

• In point-to-point mode , A producer and a consumer can only access one queue , Split table design can reduce the design complexity

• Easy to extend and maintain , Prevent a table from being damaged , The situation that affects the whole situation appears

• Primary key

queue_id A primary key

• Indexes

stay queue_name Create a unique index on the column

2.  Message table

Record all messages stored in a message queue . This table applies to point-to-point messages , That is, after a message is created by the producer , Can only be consumed by one consumer .

In case of subscription mode , The following table needs to be split into two tables , A record message content , Another piece of consumer information that records the message . A message content will correspond to multiple consumers .

• Table structure description

notes ①： Messages exceeding the maximum length will be stored in the file system , Each super long message will be saved as a file , At this time, only the absolute path of the message file is saved in this column . For very long messages , The efficiency of creation and reading will be slightly lower .

• Primary key

msg_seq, Use autoincrement columns as primary keys

• Indexes

idx1(msg_id), unique index , It is convenient for consumers to confirm that after the message is consumed , Modify the message status using .

idx2(status,msg_seq), It is convenient for consumers to query the messages that have not been consumed , Query unused msg_seq The smallest news , Ensure that messages in a fragment are first in first out .