The proposed tech behind for the backend is: Python Flask and AWS DynamoDB
Self explanatory, takes email, hash
Returns personal data, takes session_token
Returns all matches, takes session_token
Returns public user data, takes id
Matches with user, takes id
Returns nearby people, takes coordinates
Returns your current messages, takes id, session_token
Sends a message to a user, takes id, session_token, target_user_id
These need to be fleshed out
- User
- Matches
- Chat, https://stackoverflow.com/questions/39488727/best-way-to-store-chat-messages-in-elasticsearch I propose for handling the Chat storage and schema we use the ideas presented in the above stackoverflow link for creating a facebook like chat schema using elasticsearch. i have done this before for a similar application and it works nicely. - @phara23
- New message
- New match