Relational Data Modelling | Schema Design Using Linkedin | Exclusive Tips & Tricks 2023

🔹About our System Design Series:

Our System Design Series will help you become better at the skills required to transition from an entry-level engineer to Senior Engineer and eventually become a software architect. We cover a series of topics ranging from schema design, basics like CAP Theorem, Consistent Hashing, overall system design like Facebook Messenger. When you cover these topics, you will be able to intuitively come up with practical solutions to real-life problem statements at your workplace. Our exclusive video will also be able to crack system design interviews at top tech companies like Facebook and Google.

🔹About Relational Data Modelling
The relational model in DBMS is an abstract model used to organize and manage the data stored in a database. It stores data in two-dimensional inter-related tables, also known as relations in which each row represents an entity and each column represents the properties of the entity.

🔹About Schema Design
Schema design is the process of creating a blueprint for a database, specifying the tables, fields, data types, and relationships between them. It defines the structure of the database and provides guidelines for creating and maintaining the database. It helps to ensure data integrity, consistency, and performance, and allows for efficient querying and data retrieval.

🔹About the instructor:

Mohit Yadav (ex- Nutanix, Hotstar) is an instructor at Scaler and has built systems that handle 10M concurrent users and ingest more than 1 TB of data per day. Having cleared interviews for Senior Engineer roles at companies like Facebook, Amazon, Google, and after interviewing more than 200 candidates at Hotstar and Nutanix, Mohit decided to make this video covering the #1 skill-gap that he observed in most engineers.

The following topics are covered in this video 👇🏼

0:00​ Introduction
1:14 Steps for designing Schema for Relational Database
1:50​ Creating our 1st entity
3:19 Modeling Many to Many relationships
5:40​ Splitting similar entities into two tables
9:01 Modeling One to Many relationships
10:00​ Modelling bi-directional relationships
11:51​ Combining two entities into one
13:58 Conclusion

---------------------------------------- About Scaler --------------------------------------------------

We are a tech-focused upskilling and reskilling platform catering to tech enthusiasts in universities and working professionals. There are more Scaler graduates working at Amazon than all of the IITs combined!

📌 Follow us on Social and be a part of an amazing tech community📌

🔔 Hit that bell icon to get notified of all our new videos 🔔

If you liked this video, please don't forget to like and comment. Never miss out on our exclusive videos to help boost your coding career! Subscribe to Scaler now!

#relationalschema #schemadesign

[jiyanaadlakha]

In Education/Institution and Company tables we are storing end and start date which might not be valid for a large number of users also may not be applicate for say more than 1 user also so we can have userid as foreign key also in these tables, which states one to many relation rather than many to many relationship.

[ViratSingh-nqok]

Super helpful and easy to understand. Thank you!

[akhilreddybandi]

Nice explanation.

Looking forward for a video on when to use SQL and when to use NO-SQL.

[DesiTravelographer]

Worth to Watch, learnt new thing today ... Thanks

[ayyapusettynk]

Really a great video and worth watching

[shubhisingh]

This was really helpful. Looking forward to more.

[bharaniakella]

This video is extremely helpful. Looking forward to more videos on Databases

[hemachel]

really helpful video. please add more videos on Schema Design

[MUSKAN]

Your explanation was very good! Can you please make more videos with more examples? Thanks!!

[the_silver_liningg]

That was awesome and super helpful! Thank you

[venkateshkannan]

Just few minutes into the video and can tell it’s going to be 🔥. Appreciate the effort, thank you!

[jiyanaadlakha]

instead of calling the column_name user_id_1, user_id_2 it will be better to say follower_user_id (foreign key (user_id ) in table user) and followed_user_id (again foreign key (user id)). Also the concept of foreign key is very imp in one to many relationships I believe.

[MohammedIrfan-gybv]

Wow Presentation and UX embedded is different level... great job on these enhancements...

[VeronicaSantos]

Very nice example and explanations. I missed an Entity Relationship Diagram (ERD) to see the big picture.

[poojasikdar]

Good content. Probably Entity can be a different table as well and entity IDs can be used as the reference in the other table.

[betikuntibhargav]

Thank you very much Mohit Yadav. After watching this video I just cleared my Data base design Interview in Managerial round. I used this knowledge in Interview and the Interviewer got impressed. Once Again Thanks @Scalar for finding such a GEM.

[ggsgetafaf]

You should continue to make videos like this. Thank you

[ronakgoel]

For query like you said : find all user_id for a particular skill type (say java), if we go by 1st approach ( i.e. taking skills in the user profile itself), it will be a scan operation on the table size ( say 1 billion ) .

Can you please tell, how the later method i.e. creating the user_skills mapping table will be more efficient because again we will be having 1 billion rows in this table too, and now we have to run scan operation on 1 billion rows again if we want to find user_id with a specific skill_id.

[mayankverma]

can we call, is_accepted as is_followed_back ? As is_accepted may not mean the connection is bidirectional

[Amritanjali]

please add more videos on Schema Design