Design Notification Achitecture

[MinhxNguyen7]

Description

• Design the end-to-end architecture for signing up for and canceling notifications.

Requirements

• Add and cancel notifications on a per-course basis.
• Receive notifications in SMS (and perhaps email).

Current Notes

• PPAPI will ping us when there's a change in the database with a list of courses that changed.
• We might want to switch to a relational database to develop this along with auth.

[Douglas-Hong]

Potential relational database schema for phone numbers and course codes:

Note that we might want to change the attributes for courses and users. For example, the primary key for Course should be (course_code, quarter) instead of just (course_code). Moreover, instead of setting the primary key of User to the phone number, we can set it to some user ID.

Very basic and high-level flow for notifications: