Apache Archiva vs. JFrog Artifactory

Well suited for small organizations to medium-sized teams/organizations. Apache Archiva is well suited for:

• It acts as a central repository/proxy of the artifacts generated and used by the teams.
• It provides control on which open source repositories can be utilized by the team.
• Saves network bandwidth by reducing outbound traffic.

Apache Archiva is less appropriate for organizations where immediate support/bug resolutions are required.

Incentivized

It works at scale and a large number of accessible pipelines for searching, repository updates and indexing will become easier. JFrog provides end-to-end solutions for all DevOps needs. With this, Jfrog Artifactory specifically implements the management of highly available repositories, with a smooth interface and integration with all the main CI tools on the market.

Incentivized

• It's an open source project and therefore saves cost.
• It allows exchange of artifacts/libraries between different teams.
• It allows managing internal and external repositories with ease.

Incentivized

• Stores and Manages build artifacts and packages.
• Works as container registry as well.
• Easily manages local and remote repositories along with live replication.

Incentivized

• Muti-tenancy was hard to achieve.
• UI can be improved. Its seems bit dated.
• It is a bit tricky to setup.

Incentivized

• CI/CD integration. We understood they do have a pipeline, so our organization already started with Jenkins, and my understanding is that not many orgs are using the JFrog pipeline.

Incentivized

The main problem that seems intractable is getting the checksum of the artifact. Managing container artifacts is a game changer for us during project execution, as the container artifact type exposes all base image and Docker file steps. This makes debugging or analysis easier. Jfrog Artifactory provides promotion feature and can automated from one environment repo to another environment repo before the deployment occurs.

Incentivized

Support tickets take days to respond. The most basic of questions that should be knocked out in a few hours don't get answers for days. Tickets are also closed without resolution.

• Apache Archiva is a great choice for organizations with a limited budget.
• Alternatives are expensive to acquire Archiva comes offers REST API(s) which allows the creation of customized UI.
• With Apache Archiva, it is easy to manage the remote proxy repositories.
• RBAC helps with managing user access to the repository.
• Configuration can be achieved using UI and stored in archiva.xml.
• Backup of configuration is quite simple.

Incentivized

JFrog pipelines are being used in the same ecosystem as an integrated environment, to support CI-CD devops journey. This eventually helps the existing team to use both the features of the same product in a seamless way.Similar Xray, can be used as a secure measure to protect your containers and can be used as a Static Code analysis tool which can also be integrated in a Devops CI pipeline as a Left shift security strategy.

Incentivized

• The impact of Apache Archiva on ROI has been positive. Since it is open source. It is free.
• It has allowed teams to store artifacts centrally, thus leading to a reduced need for multiple servers
• Security audits can be easily performed on the artifacts.

Incentivized

• We now have a solid, reliable binary repository that can survive a regional outage in AWS when deployed properly
• It has allowed us to focus on building mature CICD pipelines without having to worry about an unreliable binary repository.

Incentivized