Databases
StackOverflow2013
Postsdbo
PODesign pattern : notification system
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODesign pattern : notification system
    primarykey
    data
    text
    <p>I'm working on a website that will use features of social networking (like facebook for example).</p> <p>I would like to implement a notification system which shows stuff like "X added you as a friend", "Y invite you to the party", "Z has taken the lastest quizz"... and i don't know how to do.</p> <p>I wonder what is the best solution :</p> <ul> <li>Solution 1, aka "logging".</li> </ul> <p>A dedicated table "notification". I add rows in this table everytime something that rise a notification happend (friend adding, quizz answering, etc.). The table "notification" has fields that contains different information, according to what kind of notification is added to the table.</p> <p><strong>Good</strong> : easy to code, separation between notification feature and "normal" features, not too much resources-consuming when i need to read the table.</p> <p><strong>Bad</strong> : Notification table will grow probably very big (i think I will add 10k rows/day in the table), "duplicated" information : informations in the notification table can be found in all other table using date/list/whatever comparison.</p> <ul> <li>Solution 2, aka "look everywhere".</li> </ul> <p>Everytime i need to show the notification list or the show how much new notifications there are, I look to all the concerned table, compare date/etc to know if something new happened since the last time the user checked the notification.</p> <p><strong>Good</strong> : Not a too big table compared to solution 1, no "redundancy" of information.</p> <p><strong>Bad</strong> : I am affraid because of the number of user (~1k+), it make the server explode because it is resource/time consuming, little harder to code/maintain.</p> <p>Can you please tell me what you think the better and why, or do you have a solution i didn't imagined ?</p> <p>Thanks =)</p> <hr> <p><strong>Edit :</strong> Let's say i use a really basic DB design : users have friends, can do quizzes. 1 table for user list, quizz list, 1 table quizz&lt;->user relation, 1 table user&lt;->user for friendship. Everytime a user visit his own profile, he can see what happened : new quizz&lt;->user relation, new user&lt;->user relation, etc. How would you design a notification like that ?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USClement Herreman
    1. USClement Herreman
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODesign pattern : notification system
      1. USLior Cohen
      1. VTFavorite
    2. VO
      singulars
      1. PODesign pattern : notification system
      1. USHarri Siirak
      1. VTFavorite
    3. VO
      singulars
      1. PODesign pattern : notification system
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload