Building LinkedIn's Next Generation Architecture with OSGi

This document discusses LinkedIn's adoption of OSGi to address challenges with their growing architecture. Some key challenges included a monolithic codebase, slow feature development, and difficulties upgrading services. OSGi was seen as a solution to allow: [1] dynamic deployment of services, [2] shared libraries across containers to improve efficiency, and [3] transparent service location across containers. However, the document also notes problems with OSGi including immature tooling, difficulty managing versions, and limitations of its container-centric design. Overall LinkedIn is moving to adopt OSGi but also working to address problems and "hide" complexity from application developers.