Azure Artifacts vs. Docker vs. JFrog Artifactory

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

You are going to be able to find the most resources and examples using Docker whenever you are working with a container orchestration software like Kubernetes. There will always some entropy when you run in a container, a containerized application will never be as purely performant as an app running directly on the OS. However, in most scenarios this loss will be negligible to the time saved in deployment, monitoring, etc.

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

• 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

• Packaging of application to limit the space occupied
• Ease of running the application
• Provide multiple ways to handle the application issues and integration of different components like pipeline, ansible, terraform etc

• Artifactory Management acting as a repository manager of docker images, application and component dependencies
• Automate pipelines and thereby releasing changes faster
• Supports high availability and scalability with multi site replication

Incentivized

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

Incentivized

• Docker hub image retention policy can be relaxed
• Docker hub policies can be more developer friendly
• Docker CLI help section can be improved
• Image and container storage (local) management can be optimized

Incentivized

• We can always use support for more different types of packages in Artifactory.
• We also would like to see the Artifactory X-Ray produce continue to mature.

Incentivized

I have been using Docker for more than 3 years and it really simplifies the modern application development and deployment. I like the ability of Docker to improve efficiency, portability and scalability for developers and operations teams. Another reason for giving this rating is because Docker integrates CI/CD pipelines very well

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

Haven't seen any outages, fatal/unrecoverable errors in my usage so far. Enough said.

Incentivized

Docker Desktop. The CPU high usage is a known issue. Needs fixing. Otherwise, it is great overall. Would not use anything else still.

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.

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

The reason why we are still using Docker right now is due to that is the best among its peers and suits our needs the best. However, the trend we foresee for the future might indicate Amazon lambda could potentially fit our needs to code enviornmentless in the near future.

Incentivized

JFrog Artifactory has a much more friendly GUI, making package exploration less of a chore to do. Other than that, their features are pretty much comparable to each other. Both support multiple types of packages; both have API that can integrate well with CI/CD pipelines.

Incentivized

It is the only tool in our toolset that has not [had] any issues so far. That is really a mark of reliability, and it's a testimony to how well the product is made, and a tool that does its job well is a tool well worth having. It is the base tool that I would say any organisation must have if they do scalable deployment.

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

• Reduces the number of virtual machine which impacted our quarterly billing
• Using docker with proxy we run multiple application on same port on same host.
• impact on billing is we have to provide docker training to the people who are working on it.

• So many times it happens at the time of dependency resolution some of the servers are down e.g NPM, Maven central, PiPy in that cause our builds starts failing. By proxying these repositories with JFrog this is never happened again.
• It reduced the additional cost of container image registry and management effort.
• Support of integration with Build, Monitoring, and CI tools resulted in smooth automation and management.

Incentivized