Message queue MySQL table that stores message data

Design thinking

General description

Three types of tables are required ,

• A table describing the meta information of each message queue , Contains basic information about the queue , And queue configuration , Just a watch ;

• Record the consumer information subscribed to each message queue

• The specific message content table in the message queue ,
  One table per queue
  .

The first advantage of this design is that the data between queues does not affect each other , Second, the data volume of the table will not grow very fast , The total amount will not be very large .

Process description

• Create a new message queue ： Record the queue name and configuration to meta surface

• Consumers subscribe to message queues ： Record client information to subscriber surface , It is convenient to notify consumers after subsequent messages enter the queue

• The message arrives at the message queue ： According to the queue name , Find the message content table corresponding to the queue , Record the message id、 Message content to message surface

• Inquire about subscriber surface , Find the subscriber of the queue ip Etc , Send notification of arrival of new messages

• Consumers get messages , The customer service end queries the messages that have not been consumed , The queue passes subscriber The largest message recorded in id, Will be greater than the maximum message id The message is returned to the client

Table design

Queue meta information table

Table name ：queue_meta

Field ：

• id： queue ID

• name： Queue name

Subscription table

Record the maximum messages each consumer currently consumes id

Message content table