![]() As we built out features, the repository grew organically according to the product needs, much like most projects. When we first began developing what is now our largest Talent Solutions product suite, the frontend codebase was structured as a classic monolithic application. This monumental task is made possible by our ongoing efforts to invest in building consistent, quality code at scale. These suites of products enable recruiters, job seekers, and enterprises to source, connect, and hire talent from LinkedIn’s economic graph, generating eight hires a minute on LinkedIn. We own the foundations of this ecosystem and build distributed, highly scalable products that connect talent with opportunity at a massive scale. LinkedIn Talent Solutions is the central piece of our hiring ecosystem, which houses a broad spectrum of products including LinkedIn Recruiter, Jobs, Talent Hub, Career Pages, Talent Insights, and more. In the face of challenging productivity problems, our LinkedIn Talent Solutions (LTS) teams recently adopted yarn workspaces, unlocking a 97% improvement in lead time for delivering commits to our deployment pipeline, reduced from 39 hours to 125 mins. Our infrastructure teams enable developers to work effectively within these large applications without being impacted by the sheer scale of each codebase. ![]() At LinkedIn, we develop many applications that receive regular contributions from a multitude of teams, with each team owning distinct products or features. While many projects start small with just one or two repositories (for example, frontend and backend), this approach often becomes difficult to maintain as the codebases expand. As teams and applications experience growth, it’s critical to adopt architectures that optimize for clear code ownership, build isolation, and provide efficient delivery of code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |