To create a SeaS vertical, a SeaS-’xyz’ multiproduct (MP) is to be set up by the application team. A search use case that has been set up using this solution is referred to as a SeaS vertical, and LinkedIn application teams have been leveraging it for setting up search verticals since 2014. The SeaS library predominantly contains the logic related to the lifecycle of services and their interactions across a search cluster while the Galene library contains low-level inverted index logic, notably, the logic related to retrieval and management of live updates to the data that has been indexed. LinkedIn’s legacy search solution is built on top of SeaS (Search as a Service) and Galene libraries. In this post, we will talk about Hosted Search, our new search solution that allows product developers to integrate search functionality with minimal onboarding and no maintenance or operational overhead, allowing them to instead focus on their products and what they care about most: creating value for our members. As data needs grow and an increasingly high number of products want to integrate search, we discovered a need for a fully managed self-service platform to completely democratize search for all of our product teams. We have long provided a central platform for search functionalities however, it was not fully managed in the sense that the application teams needed to own and operate the corresponding resources. Search functionality is a core part of most data-driven products, and is used widely at LinkedIn.

Linkedin search