[RFC] Entities required for Skill tree

[vikhyat187]

Problem statement: We wanted to store the skill details of a user, these skills can be endorsed by other developers. An endorsement after approval from the super user gets showed on user skills.

List of Entities

• Skill
• Endorsements
• EndorsersList
• Users (already exists)
• UserSkill Mapping

Entity relations

• User -> Skill (1 : N) [we store it in UserSkillMapping]
• Endorsement -> skill (1 : 1) [skill Id stored as fk in endorsement table]
  

[vikhyat187]

To work with Sql on scale the things to keep in mind

1. Having no SPOF (Multi AZ deployment)
2. Horizontal scaling the database (Sharding)
3. Separating the reads from master node (using read replicas)
4. Using proper indexes on data

Costing wise AWS RDS > AWS Dynamodb

[DashDeipayan]

[DashDeipayan]

Updated ER Diagram

NB: All entities have a created_at/by and updated_at/by field

[iamitprakash]

@DashDeipayan what about users, endrosements,user_skills table.....

[DashDeipayan]

Updated ER Diagram