Overview
This article discusses the development of a LinkedIn application within an OpenSocial container, detailing the architecture, technologies used, and the author's experiences during their internship. It highlights the integration of LinkedIn's REST APIs and the use of Ruby on Rails to create a prototype that was later deployed for millions of users.
What You'll Learn
1
How to create an OpenSocial application using Ruby on Rails
2
Why caching user data with memcached improves application performance
3
How to implement OAuth for secure API access
Prerequisites & Requirements
- Basic understanding of Ruby on Rails and REST APIs
- Familiarity with memcached and MySQL(optional)
Key Questions Answered
What is the purpose of the OpenSocial application developed for LinkedIn?
The OpenSocial application allows users to access LinkedIn data and functionality outside of linkedin.com. It enables users to view connections, check network updates, browse profiles, post comments, share articles, and send invitations, enhancing user engagement across different platforms.
How does the architecture of the LinkedIn OpenSocial app function?
The architecture includes a Ruby on Rails backend that communicates with LinkedIn's REST APIs to fetch user data. It employs memcached for caching user data and MySQL for storing OAuth access tokens, ensuring efficient data retrieval and performance.
What technologies were used in building the LinkedIn OpenSocial application?
The application was built using Ruby on Rails for the backend, memcached for caching, and MySQL for data persistence. The integration with LinkedIn's REST APIs was facilitated through an OAuth wrapper created by the author.
Technologies & Tools
Some links below are affiliate links. We may earn a commission if you make a purchase.
Backend
Ruby On Rails
Used to build the application and communicate with LinkedIn's REST APIs.
Caching
Memcached
Employed to cache user data for improved application performance.
Database
Mysql
Used to persist user’s OAuth access tokens.
Security
Oauth
Implemented for secure communication with LinkedIn's APIs.
Key Actionable Insights
1Utilize memcached to cache frequently accessed user data to enhance performance.Caching reduces the load on the database and speeds up data retrieval, which is crucial for applications with a large user base.
2Implement OAuth for secure API access to protect user data and maintain privacy.OAuth is a widely accepted standard for authorization, ensuring that users can safely grant third-party applications access to their data without sharing their credentials.
3Leverage the OpenSocial framework to create applications that can be embedded across various platforms.This approach allows for greater user engagement and accessibility, as users can interact with LinkedIn features from different websites.
Common Pitfalls
1
Neglecting to properly secure API access can lead to unauthorized data exposure.
Using OAuth correctly is essential to ensure that user data remains protected. Failing to implement it can result in security vulnerabilities.
Related Concepts
Opensocial Applications
Oauth Security
API Integration