Answers: <ol>
  <li>Saved bandwith and faster downloads: Artifactory stores the artifacts that are downloaded from maven central. So if another developer needs the same dependencies they don't need to be downloaded again from maven central but instead they can be delivered from the local artifactory instance.
  This makes downloading faster because company networks are usualy faster then the internet connection and it also saves bandwith.<br />
  As example imagine that a developer adds a new dependency to a project. This dependency then needs to be downloaded into the local maven cache of every other developer that is working on the same project.
  On large projects with a lot of developers this means that the dependency might be downloaded 30 times.</li>
  <li>Stable builds: Dependencys might be removed from maven central. If you have them in your local artifactory instance the project who depends on it can still be build.</li>
  <li>Easier maintenance: Another benefit that has nothing to do with maven: Artifactory provides several types of repositories like for Docker or Vagrant.
  So instead of setting up a maven artifacts repository, a docker registry and some kind of vagrant store you could create three repositories in artifactory.
  Thus you only need to maintain one application (artifactory) instead of three separate applications.</li>
  </ol>
  <p>Some or all of these benefits might also apply to other binary repository managers but as I only know artifactory I can't say something about that.</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-04-19T13:56:03.647Z
Answers: @Thanks for a good answer.
Answers: jerry383
Answers: CC BY-SA 4.0
Answers: 2021-04-20T16:20:57.580Z
Answers: @jerry383 If my answers has satisfied your needs I would be happy if you mark it as accepted answer so it doesn't pop up in the unanswered questions list.
Answers: jadephantom
Answers: CC BY-SA 4.0
Answers: 2021-04-20T19:33:07.143Z
Answers: @jadephantom Thanks for your excellent answer.  I would also highlight security.  I think that's often a driving factor in adopting private repos.
Answers: chicks
Answers: CC BY-SA 4.0
Answers: 2021-04-19T07:39:55.480Z
Answers: 2021-04-19T08:12:39.243Z
Answers: 2021-04-19T08:12:39.243Z
Answers: jadephantom
Body: <p>I have usually seen that when someone uses Maven on a company network to download dependencies, then user is redirected to the JFrog Artifactory or any other, instead of downloading dependencies from official Maven Central Repository.</p>
  <p>What's the benefits to companies/organisations using other Repositories like JFrog?</p>
  
Tags: <build-pipeline><builds><maven><artifactory><dependency-management>
Title: Why do companies use JFrog Artifactory or other repositories instead of Maven central repository?
UserDisplayName: jerry383
ThreadText: # Why do companies use JFrog Artifactory or other repositories instead of Maven central repository?
  
  (Asked by: username_0 on 2021-04-19)
  
  I have usually seen that when someone uses Maven on a company network to download dependencies, then user is redirected to the JFrog Artifactory or any other, instead of downloading dependencies from official Maven Central Repository.
  
  What's the benefits to companies/organisations using other Repositories like JFrog?
  
  **Tags:** build-pipeline, builds, maven, artifactory, dependency-management
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-04-19. Score: 5
  
  1. Saved bandwith and faster downloads: Artifactory stores the artifacts that are downloaded from maven central. So if another developer needs the same dependencies they don't need to be downloaded again from maven central but instead they can be delivered from the local artifactory instance.
     This makes downloading faster because company networks are usualy faster then the internet connection and it also saves bandwith.  
     As example imagine that a developer adds a new dependency to a project. This dependency then needs to be downloaded into the local maven cache of every other developer that is working on the same project.
     On large projects with a lot of developers this means that the dependency might be downloaded 30 times.
  2. Stable builds: Dependencys might be removed from maven central. If you have them in your local artifactory instance the project who depends on it can still be build.
  3. Easier maintenance: Another benefit that has nothing to do with maven: Artifactory provides several types of repositories like for Docker or Vagrant.
     So instead of setting up a maven artifacts repository, a docker registry and some kind of vagrant store you could create three repositories in artifactory.
     Thus you only need to maintain one application (artifactory) instead of three separate applications.
  
  Some or all of these benefits might also apply to other binary repository managers but as I only know artifactory I can't say something about that.
  
  > **Comments:**
  > **username_0**: @Thanks for a good answer.  
  > **username_1**: @username_0 If my answers has satisfied your needs I would be happy if you mark it as accepted answer so it doesn't pop up in the unanswered questions list.  
  > **username_2**: @username_1 Thanks for your excellent answer.  I would also highlight security.  I think that's often a driving factor in adopting private repos.  
  
  ---
  
  