Questions about the design of the Mysql User message system

1. the current website has two types of messages: full-site message and private message. (If private messages are relatively well designed, do not repeat them. The key is full-site messages. n * m design estimates that member tables will pop up ...) 2. expected results: {code ...} how should we design it? 1. the current website has two types of messages: full-site message and private message. (If private messages are relatively well designed, do not repeat them. The key is full-site messages. n * m design estimates that member tables will pop up ...)

2. expected results:

1. Users can delete messages freely. 2. you can determine the number of unread messages currently. 3. SAVE database resources.

How should we design it?

Reply content:

1. the current website has two types of messages: full-site message and private message. (If private messages are relatively well designed, do not repeat them. The key is full-site messages. n * m design estimates that member tables will pop up ...)

2. expected results:

1. Users can delete messages freely. 2. you can determine the number of unread messages currently. 3. SAVE database resources.

How should we design it?

Mysql cannot be used in this case.
At least redis must be used.