Message queue design based on mysql

< h2> message queue design < / h2>< h3> store message data & have spentMySQL Form < / h3>< h4> table name < / h4>< h5> message table < / h5>< div>< code> {topic} _message < / code>< / div>< br>< div> all queue table, using the topic.< / div>< h6> field < h6>< img SRC="/ / img.inotgo.com/imagesLocal/202207/31/202207312237176589_0.png" Alt="" loading=" lazy ">< br>< h6> why < h6>< ul>< li>< div> if a topic a table, is likely to each table in the actual production load is different, can cause uneven distribution of resources waste.The number of messages and if there is a table of growing quickly, horizontal or vertical expansion, because each topic has table itself, will further increase the complexity of the table management.< / div>< / li>< / ul>< ul>< li>< div> will be on the primary key as the index, is advantageous to the mysql query and write quickly, avoid the loss of performance.< / div>< / li>< / ul>< h5> subscription form < / h5>< div>< code> subscribe_info < / code>< / div>< div> record user subscription information, based on the users subscribe to quality and service condition, etc. To subscribe to push.< / div>< h6> field < h6>< img SRC="/ / img.inotgo.com/imagesLocal/202207/31/202207312237176589_1.png" Alt="" loading=" lazy ">< br>< br>