Architecture Battalion Module 8 Homework

Design a MySQL table for storing message data in a message queue

[Job Requirements]

1. IncludeTable name, field, index;

2. Use text to describe design ideas and reasons, such as: Why design an index?

3. One page PPT is enough.

[Tips]

1. Need to consider one table for each message queue or one table for all messages, which adds a "Queue Name" field.

First, the design scheme

Considering the performance of MySQL single table, each message queue is used to save a separate data table.

• Advantages:

• The queues are decoupled and data isolated.

• Simple implementation and high performance.

• Disadvantages:

• requires more resources than a singlesurface.

• The maintenance cost is slightly higher than the single-table solution.

1.1 Table Design

1.1.1 Table Name Rules

Table Name:

{topic}_message

Description: One table per queue, the data table is generated when the topic is created.

1.1.2 Field Design

1.2 Processing logic

1.2.1 Production message

• Message queue service acquisition
  TOPIC name
  and
  message body
  and processed after
  .

• According to the table name rules, find the corresponding message table from
  TOPIC name
  to write dataIf the table is not found, a new table is created.

1.2.2 Consumption message

The consumer node polling and pulling the consumption status is

Unconsumed

The data of the

is consumed.

Update after successful consumption

Consumption time

and modify the consumption status to

Consumed

.