Home > other >  The realization of the backend system to push the message at the front desk users receive notificati
The realization of the backend system to push the message at the front desk users receive notificati

Time:12-05

I now do a flask of foreground system and background, the background system administrator to push notification to the front desk of all users, push after success in the top right-hand corner of the front desk system shows that the number of unread messages; Is thinking the backend system maintenance a notification message table, the front desk system maintenance a user associated with the notification message list, and then push every time the background, will write to the all users associated list?
So if that's the case, if there are 10000 users, push a notification needs to write 10000 records, database under a lot of pressure

CodePudding user response:

Can a notification corresponds to a sent the user id of separator connection string
For example:
Notice 1, id1 | id2 id3 | | id100
Notice 2, id1 | id6 | id20

CodePudding user response:

reference 1st floor chuifengde response:
can be a notification corresponds to a sent the user id of separator connection string
For example:
Notice 1, id1 | id2 id3 | | id100
Notice 2, id1 | id6 | id20

After users receive the message, and the state of the message? The message unread or read, so there should be a message status field...

CodePudding user response:

  • Related