Answers: <p><strong>What is Git-LFS?</strong></p>
  
  <p>Git Large File Storage (LFS) prevents that large files need to be stored in git itself.</p>
  
  <p><a href="https://git-lfs.github.com/" rel="nofollow noreferrer">https://git-lfs.github.com/</a></p>
  
  <blockquote>
    <p>Git Large File Storage (LFS) replaces large files such as audio
    samples, videos, datasets, and graphics with text pointers inside Git,
    while storing the file contents on a remote server like GitHub.com or
    GitHub Enterprise.</p>
  </blockquote>
  
  <p><strong>What is artifactory?</strong></p>
  
  <p>Artifactory stores artifacts, e.g. docker images, jars, wars</p>
  
  <p><strong>Artifactory vs. Git-lfs</strong></p>
  
  <p>Artifactory is used to store artifacts while git-lfs is used to prevent that large files are stored in git. If one will store large files in git and one would like to clone this repository it will take a decade before it is cloned.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-10-03T16:18:20.750Z
Answers: 2017-10-03T16:18:20.750Z
Answers: 030
Body: <ul>
  <li>Git lfs is just support for large files in Git -> good for example for a video file sample if you need it, right?</li>
  <li>But, if you have large artifacts like a trained model or an uber-jar or some other artifact, what is the benefit to version this binary in git? </li>
  </ul>
  
Comments: CC BY-SA 3.0
Comments: 2017-09-15T10:02:00.867Z
Comments: Answer is in the question: versioning... `lfs` is more or less just replacing the actual file in the repo by a text pointer to the real file in a repository, more details [here](https://git-lfs.github.com/)
Comments: Tensibai
Comments: CC BY-SA 3.0
Comments: 2017-09-15T16:59:17.123Z
Comments: Related comment discussion: https://devops.stackexchange.com/questions/1999/data-science-pipelines-and-monolitic-model-blobs/2001#2001
Comments: Dan Cornilescu
Tags: <artifacts><methodology><artifactory><git-lfs>
Title: Can we consider usage of git lfs for artifacts equally mature strategy to an artifactory?
UserDisplayName: Ta Mu
ThreadText: # Can we consider usage of git lfs for artifacts equally mature strategy to an artifactory?
  
  (Asked by: username_0 on 2017-09-15)
  
  * Git lfs is just support for large files in Git -> good for example for a video file sample if you need it, right?
  * But, if you have large artifacts like a trained model or an uber-jar or some other artifact, what is the benefit to version this binary in git?
  
  **Tags:** artifacts, methodology, artifactory, git-lfs
  
  > **Comments:**
  > **username_1**: Answer is in the question: versioning... `lfs` is more or less just replacing the actual file in the repo by a text pointer to the real file in a repository, more details [here](https://git-lfs.github.com/)  
  > **username_2**: Related comment discussion: https://devops.stackexchange.com/questions/1999/data-science-pipelines-and-monolitic-model-blobs/2001#2001  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2017-10-03. Score: 1
  
  **What is Git-LFS?**
  
  Git Large File Storage (LFS) prevents that large files need to be stored in git itself.
  
  <https://git-lfs.github.com/>
  
  > Git Large File Storage (LFS) replaces large files such as audio
  > samples, videos, datasets, and graphics with text pointers inside Git,
  > while storing the file contents on a remote server like GitHub.com or
  > GitHub Enterprise.
  
  **What is artifactory?**
  
  Artifactory stores artifacts, e.g. docker images, jars, wars
  
  **Artifactory vs. Git-lfs**
  
  Artifactory is used to store artifacts while git-lfs is used to prevent that large files are stored in git. If one will store large files in git and one would like to clone this repository it will take a decade before it is cloned.
  
  
  ---
  
  