Add Git (As a Protocol)

Git-%28As-a-Protocol%29.md

@@ -0,0 +1,22 @@
+Git is
+highly efficient in both its network protocols and hard drive storage mechanisms for source code, primarily due to its use of a content-addressable filesystem, deduplication, and delta compression. 
+Git Protocol Efficiency
+Git's network protocols (like the native Git protocol, SSH, and optimized HTTP/S) are designed for speed and minimal data transfer. 
+
+    Smart Transfers: When fetching or pushing changes, Git intelligently checks which objects (files, commits, etc.) the client and server have in common and only transfers the compressed data (deltas) that is missing. This significantly reduces bandwidth usage and speeds up operations, especially compared to older, less "smart" version control systems.
+    Protocol Options: The native Git protocol is often the fastest due to less overhead (no encryption or authentication) but is usually limited to public, read-only access. Other protocols like SSH and HTTPS are also efficient and provide necessary security features for private repositories.
+    Performance at Scale: For very large repositories or high-traffic projects, the efficiency of Git's protocols becomes crucial, and optimizations like Git protocol version 2 further improve performance by filtering unnecessary references during data transfer. 
+
+Git Storage Efficiency
+On the hard drive, Git's storage model is also highly optimized for source code (mostly text files with incremental changes). 
+
+    Snapshots, not Diffs (Conceptually): Git conceptually stores a complete snapshot of the project at each commit. However, it avoids data duplication on the disk.
+    Content-Addressable Storage: Git stores content as "blobs" identified by a SHA-1 hash of their content. This means if a file's content hasn't changed, it isn't stored again; a new commit just links to the existing blob, achieving perfect deduplication.
+    Delta Compression: While Git initially stores new or modified files as zlib-compressed "loose objects," a background process (garbage collection, git gc) combines these into "pack files". Within pack files, Git applies delta compression, storing subsequent versions of a file as only the differences (deltas) from a similar, older version, greatly minimizing space usage.
+    Performance with SSDs: Git operations involve a lot of disk I/O to access its object database, so it generally performs better on a Solid State Drive (SSD) compared to a traditional spin disk. 
+
+Limitations
+Git is highly efficient for typical source code, but its efficiency can be impacted by: 
+
+    Large Binary Files: Git stores every version of large binary files (e.g., images, large datasets, compiled executables) in the history, which can make repositories very large and slow down operations like cloning. The recommended solution is to use [Git Large File Storage (LFS)](https://git-lfs.com/) to manage them efficiently.
+    Extremely Large Codebases: While generally efficient, exceptionally large codebases with high commit volumes may require specific performance tuning or specialized tools to avoid bottlenecks