AWS CodeDeploy vs. JFrog Artifactory

Getting the code from Git Hub, uploading it to the repository, making changes, and deploying it to a specific environment makes AWS tremendous and easy to work with. Once you know how to do it, it is easy to replicate. On the other hand, if you are new, it gets confusing, and you need guidance on the steps to take not to compromise the application.

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

• Integration with other AWS services
• No administration required
• Unified and easy process for dev teams

Incentivized

• 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

• There is one limitation is it can't do multi-tier apps
• It is not possible to control the order in which deployment occurs if more than one deployment attempts to run at the same time
• AWS CodeDeploy does not integrate with GitHub

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

Here is where AWS as a whole stepped up big. The UI is more intuitive and easy to use. The separation is clear, and the guides are abundant. They still need to create starter tutorials for newcomers so we don't lose much time learning/teaching others. Having someone with basic knowledge and examples where they can gain experience will make it better.

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.

Jenkins supports a lot of plugings. Also with Jenkins, it is possible to manage everything through our own server. Those are 2 points where I rate Jenkins as one of the best DevOps Tool

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

• AWS CodeDeploy has reduced the engineer involvement in deployments
• Our QA team has been able to effectively deploy tickets for testing, and our Release Managers can manage production deployments
• Progress indicators have given us a better baseline for deployment times, which is helpful for time-sensitive releases

Incentivized

• 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