𝗪𝗵𝘆 𝗚𝗼𝗼𝗴𝗹𝗲 𝗦𝘁𝗼𝗿𝗲𝘀 𝗕𝗶𝗹𝗹𝗶𝗼𝗻𝘀 𝗼𝗳 𝗟𝗶𝗻𝗲𝘀 𝗼𝗳 𝗖𝗼𝗱𝗲 𝗶𝗻 𝗮 𝗦𝗶𝗻𝗴𝗹𝗲 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆 Google’s monolithic repository provides a common source of truth for tens of thousands of developers worldwide. They use it for 95% of their source code, leaving Google Chrome and Android on their specific ones. They used CVS and, after some time, migrated to Perforce and later replaced it with 𝗣𝗶𝗽𝗲𝗿. The 2016 source says it has more than 𝟮 𝗯𝗶𝗹𝗹𝗶𝗼𝗻 𝗹𝗶𝗻𝗲𝘀 𝗼𝗳 𝗰𝗼𝗱𝗲 𝗮𝗻𝗱 𝟰𝟬,𝟬𝟬𝟬 𝗰𝗼𝗺𝗺𝗶𝘁𝘀 𝗽𝗲𝗿 𝗱𝗮𝘆 by more than 10,000 engineers. Engineers mainly use 𝘁𝗿𝘂𝗻𝗸-𝗯𝗮𝘀𝗲𝗱 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝗺𝗼𝗱𝗲𝗹𝘀 at scale with much success. Regarding branching, changes are pushed to the main branch and submitted to code reviews. All of this removes nightmares of merge hell. 𝗧𝗿𝗶𝗰𝗼𝗿𝗱𝗲𝗿 carries out the first automatic checks when they try to submit new code and provides initial automated feedback to the developer. And then, code review can be done using the Critique tool for code reviews. Engineers use 𝗥𝗼𝘀𝗶𝗲, a solution for massive refactorings, optimizations, code cleaning, and other tools. It enables changes to be divided into minor changes and reviews by each owner before being built. Some 𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 of this approach are: 🔹 𝗨𝗻𝗶𝗳𝗶𝗲𝗱 𝘃𝗲𝗿𝘀𝗶𝗼𝗻𝗶𝗻𝗴 🔹 𝗘𝘅𝘁𝗲𝗻𝘀𝗶𝘃𝗲 𝗰𝗼𝗱𝗲 𝘀𝗵𝗮𝗿𝗶𝗻𝗴 🔹 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝗶𝗲𝗱 𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝗰𝘆 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 🔹 𝗔𝘁𝗼𝗺𝗶𝗰 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 🔹 𝗟𝗮𝗿𝗴𝗲-𝘀𝗰𝗮𝗹𝗲 𝗿𝗲𝗳𝗮𝗰𝘁𝗼𝗿𝗶𝗻𝗴 🔹 𝗖𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗶𝗼𝗻 𝗮𝗰𝗿𝗼𝘀𝘀 𝘁𝗲𝗮𝗺𝘀 🔹 𝗙𝗹𝗲𝘅𝗶𝗯𝗹𝗲 𝗰𝗼𝗱𝗲 𝗼𝘄𝗻𝗲𝗿𝘀𝗵𝗶𝗽 🔹 𝗖𝗼𝗱𝗲 𝘃𝗶𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆 And 𝗱𝗶𝘀𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 include having to create and scale tools for development and execution and maintain code health, as well as the potential for codebase complexity (such as unnecessary dependencies). Do you use the monorepo approach? Check the full text in the thread. _______ If you like my posts, please follow me, @milan_milanovic, and hit the 🔔 on my profile to get a notification for all my new posts. Grow with me 🚀! #technology #softwareengineering #programming #techworldwithmilan #developers