User story: Communication between Alert/Notification service and User service

[eyeshield2110]

TODO: Write the contract (aka agree on function name and json format of message)

Requirements

• [x] The Notification service needs to call the User service to get the Users' alert preferences

Design for how alert and notification preferences is stored in User service

• User alert preferences:

  • user identifier/session identifier
  • city (either stored as geo location to differentiate cities with same names)

• User scheduled weather notification preferences:

  • user identifier/session identifier
  • city (maybe stored as a string with latitude and longitude, or as a string containing city name, state/province, country)
  • scheduled time as a 5 characters string? Like: '08:00' for 8am or '22:55' for 10:55pm . Constraint: only 5min slices.

Firebase queries the Notification needs to do on the User data

• A function that returns all distinct alert preferences as a collection or list: Ex. getAllDisctinctAlertLocations() returns

           [
                 "montreal,qc,canada", 
                 "brisbane,australia"
           ]

• A function that returns a collection of key-value pairs of location and scheduled time:
  • Ex. getAllScheduledNotifications() returns [ ]
  • Alternative: getAllScheduledNotifications() returns

         [ 
             { "montreal,qc,canada": [ "08:00", "15:05" ] },
             { "brisbane,australia": [ "12:55" ]}
         ]

Format of Pusher Beam Interests (doesn't need to be stored in User service/Firebase)

• Standardized weather alert format: alert_montreal
• Standardized weather scheduled notif format: schedule_08:00_montreal