Architecture

DB Schema

• Authentication

  • Id: string
  • Email: string
  • Password: string

• Users

  • user_id : string
    • Id: string
    • Name: string
    • Username: string
    • Email: string
    • PhoneNumber: int
    • DOB: Date
    • Photo: string
    • Socials: []
      • type: string
      • profile: string
      • sAccounts: []
        • id_push: string
        • user: string
        • url: string
    • Contacts []
      • Id: string
      • Name: string
      • Username: string
      • Email: string
      • PhoneNumber: int
      • DOB: Date
      • Photo: string
      • AccessSocials: []
        • type: string
        • profile: string
        • sAccounts: []
          • id_push: string
          • user: string
          • url: string
    • QR: []
      • q_id: string
      • u_id: string
      • Email: string
      • PhoneNumber: int
      • DOB: Date
      • Socials: []
        • type: string
        • profile: string
        • sAccounts: []
          • id_push: string
          • user: string
          • url: string

Maintaining State

• Our app will maintain state to determine if user is logged in or not. This will be done in memory.

Queries

• Create User(Auth) - uses Authorization table
• Get User Information
• Get User Socials
• Get User Contacts
• Get QR Data
• Get Contact Socials
• Update User Information
• Update User Socials
• Update User Contacts
• Put QR Data
• Put User Information
• Put User Socials
• Put User Contacts
• Delete User
• Delete User Social
• Delete User Contact

Views and UML