Over the course of the last 5 years, LinkedIn has been built using relatively simple technologies: front end web applications (tomcat/servlet/jsp), backend services (jetty/spring remoting), databases, replication, jms, ... Although the web site was scaling adequately, LinkedIn had some big challenges to overcome:
In March of 2008, a group of Senior Engineers started a project to explore the best available technologies which could help in building the next generation of the architecture that would address those challenges. The new architecture involved using OSGI/Spring DM as the foundation because it had the right properties we were interested in. The code was migrated to a more modular paradigm using binary consumption...
This session will demonstrate how we integrated OSGI, the pros and cons of the changes, the pain points as well as the migration strategy:
LinkedIn was mostly member centric, with the traditional member login / session pattern. When the need arose to open up an API, LinkedIn revisited the model in order to seamlessly integrate calls coming from the main website as well as calls coming from the APIs. This session will cover several aspects of the changes:
This talk will also cover how LinkedIn retrofitted the security model chosen for the API into the mainstream website, which helped tremendously in the scalability of the website by allowing stateless frontend / single sign on (SSO), and improved security by removing sessions entirely.
© 1997 2008 Kovsky Conference Productions Inc.; All rights reserved.