Module 8 job message data MySQL table design

Job requirements

Table design

Ideas

• Performance considerations , Use one table per queue

• Businesses often query data through the timestamp of messages , So here it is  timestamp  Field creation index

• Messages have three states ：NEW, ACKED, DELETED

DDL

CREATE TABLE `message_topic_x` (
 `id` bigint(11) unsigned NOT NULL AUTO_INCREMENT,
 `message_body` text NOT NULL,
 `status` enum('NEW','ACKED','DELETED') NOT NULL DEFAULT 'NEW',
 `publisher` varchar(200) DEFAULT NULL,
 `published_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
 `acted_at` timestamp NULL DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP,
 PRIMARY KEY (`id`),
 KEY `idx_published_at` (`published_at`),
 KEY `idx_acted_at` (`acted_at`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;