Summary: Designing LinkedIn
Get an overview of designing LinkedIn case study, covering key requirements, important classes, and design highlights.
After completing the LinkedIn case study, reviewing and reinforcing your understanding is a good time. We’ll look back at the main system requirements, outline the core classes along with their roles and relationships, and highlight the key design principles that were applied. We’ll also explore how different objects interact within the system and walk through the overall workflow to see how all the components fit together to deliver the intended functionality.
Key requirements
Here are the primary functional and non-functional requirements that define the scope of the LinkedIn system:
Users can create and update profiles with education, experience, achievements, and skills.
Users can search for other users, company pages, groups, and job listings.
Users can send, cancel, accept, or ignore connection requests.
Users can follow or unfollow other users and company pages without connecting.
Users can view analytics such as connections, profile views, post impressions, and search appearances.
Users can request and give recommendations.
Users can create, react to, share, and comment on posts and on existing comments. ...