At LinkedIn, we have traditionally maintained our source code in large, monolithic repositories (repos). While this worked for over a decade, it proved challenging to maintain and support as our repo grew larger, and issues like long build times, difficulties managing merge queues for reverts, and slow deployments led to differing levels of frustration for our...