Apache Archiva vs. Azure Artifacts vs. Helm

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

Share codes and packages across the whole organization. We have developers most of the time work from home or overseas like in India. We can test and deploy the package when they deploy the new changes into the Azure Artifacts. Azure Artifact can promote our package to the correct system like DEV, UAT, or Production. It also provides retention policies to automatically clean up expired packages.

Incentivized

If you need to automate the deployment of environments in Kubernetes and these environments should be easily replicable in other regions of your cloud provider or even in other cloud providers, then this is the tool for you. Just be prepared for a certain degree of complexity when creating the charts.

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

• Security feature on share code efficiently.
• The built in CI/CD for the software pipeline.
• Support for most famous build tool like maven and npm.

Incentivized

• Templates - The ability to create templates is really helpful and help creates a baseline for package management.
• Rollbacks - it is godsend. Period.
• Dry-run - This really is helpful when troubleshooting deployments and is great for testing out new charts as well.

Incentivized

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

Incentivized

• Native artifact format support like docker image
• Support for APL
• Support IAM permission

Incentivized

• concurrent deployments
• templating values files

Incentivized

We didn't really need support, but the open-source community seemed responsive and informative when it came to issues. Many cloud native consultancy companies (including ourselves) offer support for Helm.

Incentivized

• 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

Azure Artifact is based on GitHub which is the best artifact at all times. Helm is open source and we may have security concerns. Crucible is a good tool but does not of a lot of support. I prefer that Azure Artifact is a solid product and with a good gene from the GitHub codebase.

Incentivized

We have a natural trending to use what is a reference in its space and Helm has being leader in its area for a long time. Since it has all features we need didn't make sense to us to invest time on researching and testing other alternatives, so Helm was our first and only tool in regards of automating deployments on Kubernetes

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

• The artifact provide best practice to our software development.
• Provide a standard way to release the software.
• The package is immutability which means no one can update it after release.

Incentivized

• Reduction in human effort.
• Streamline software versions and upgrades.

Incentivized