Git is a popular open-sourced Distributed Version Control System (DVCS). Here is the design of a Git product for your understanding.

Git consists of three main states in its design. They are:

• Committed
• Modified
• Staged

The committed state refers to data safely stored in the local database. Modified is relates to change in the file/data that have not yet been committed to the database. Staged refers to marking a modified file in its current version to move it into the next commit snapshot.

Git has three core states. These defined states lead into the execution section's three categories, namely:

• Git Directory
• Staging Area
• Working Directory

To start with, the Git Directory a storing place for persisted meta data and its related object database for the relevant projects. As it is leveraged to clone a particular repository from one computer to another, it is a highly important component of any Git product.

The Staging area is a temporary placeholder, and is usually the file contained in your Git directory. It persists the information about the list of changes to be committed in the next commit cycle. It is often known as an index.

The Working directory is a placeholder for checking out the version content of a relevant project. Involved with the core process, these files are extracted from the original compressed database in the Git directory. Then, the extracted readable files are placed on the local disk of the end customer. Later, the end user can then use it for their own purpose in this working directory:

The basic Git workflow is demonstrated in the following diagram:

With a good understanding of Git's basic concepts, we can now explore the fundamentals of Microsoft's TFS product.