Codebase

This article is about the source code of software systems. For the homonymous database management system, see CodeBase.

A codebase (or code base) is a collection of source code that is maintained as a unit. Typically, it is used to build one or more software components including applications and libraries.

A codebase is often 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 either to 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 this 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

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 and kernel version 3.10)

See also

Wiktionary logo
Look up codebase, code base, codebases, or code bases in Wiktionary, the free dictionary.

References

  1. ^ "A Short History of Git". git-scm.com. Retrieved October 21, 2014.
  2. ^ 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.
  3. ^ a b "Scaling Mercurial at Facebook". Facebook Code. 2014-01-07. Retrieved 29 April 2016.
  4. ^ "Git - Distributed Workflows". git-scm.com. Retrieved 29 April 2016.
  5. ^ 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.
  6. ^ @feross (April 24, 2014). "Facebook's git repo is 54 GB" (Tweet). Retrieved 29 April 2016 – via Twitter.
  7. ^ 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.

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.