Codebase
 | This article needs additional citations for verification. (October 2014) |
A codebase (or code base) is a collection of source code that is maintained as a unit. Typically, it can be used to build one or more software components including applications and libraries.
A codebase is typically stored in a source control repository of a version control system. A repository can contain build-generated files (which are therefore not source code), but typically such files are excluded from a repository, and therefore, the codebase. A repository may contain data files (such as configuration) that are required for building or running the resulting software. But, version control is not a required aspect of a codebase. Even the Linux kernel was maintained without version control for many years.[1]
When developing multiple components, a choice is made to either maintain a separate, distinct codebase for each or to combine codebases; possibly in a single, monolithic codebase. With a monolithic codebase, changes to (i.e. refactoring) multiple components can often be easier and robust. But, it requires a larger repository and makes it easier to introduce wide-ranging technical debt.[dubious – discuss] With separate codebases, each repository is smaller and more manageable. The structure enforces logical separation between components, but can require more build and runtime integration between codebases, and complicates changes that span multiple components.[2][3][4]
Examples
[edit]Some notably large codebases include:
- Google: monolithic, 1 billion files, 9 million source code files, 2 billion lines of source code, 35 million commits in total, 86 TB total size (January 2015)[5]
- Facebook: monolithic, 8 GB (repo 54 GB including history, 2014),[6] hundreds of thousands of files (2014)[3]
- Linux kernel: distributed,[7] over 15 million lines of code (as of 2013[update] and kernel version 3.10)
See also
[edit]
References
[edit]- ^ "A Short History of Git". git-scm.com. Retrieved October 21, 2014.
- ^ J. David Morgenthaler; Misha Gridnev; Raluca Sauciuc & Sanjay Bhansali (2012). "Searching for Build Debt: Experiences Managing Technical Debt at Google". Proceedings of the Third International Workshop on Managing Technical Debt. IEEE. pp. 1–6. doi:10.1109/MTD.2012.6225994.
- ^ a b "Scaling Mercurial at Facebook". Facebook Code. 2014-01-07. Retrieved 29 April 2016.
- ^ "Git - Distributed Workflows". git-scm.com. Retrieved 29 April 2016.
- ^ Potvin, Rachel; Levenberg, Josh (24 June 2016). "Why Google stores billions of lines of code in a single repository". Communications of the ACM. 59 (7): 78–87. doi:10.1145/2854146.
- ^ @feross (April 24, 2014). "Facebook's git repo is 54 GB" (Tweet). Retrieved 29 April 2016 – via Twitter.
- ^ Sproull, Lee; Moon, Jae Yun (2000-11-05). "Essence of distributed work: The case of the Linux kernel - Moon - First Monday". First Monday. 5 (11). Retrieved 29 April 2016.