AWS CodeArtifact vs. Docker

We have a small team with limited resources and it worked well for us. Hence I can conclude that AWS Code Artifact are well suited for organizations which have limited resources in terms of hardware and access to administrators for setting up artifact repository in-house. AWS Code Artifact is also suited particularly well for organization(s) which are already using AWS Services/Infrastructure (eg. EC2) . It works quite well with existing AWS services and completes the gap which existed in AWS offering for quite some time. Organizations can move their entire DevOps toolchain and infrastructure to Amazon. It is less appropriate for organization(s) which rely on artifacts like Debian, C/C++, Go etc as AWS does not support those fully.

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

• Code Artifact is a cloud based artifact repository so there is no installation required.
• Code Artifact comes with out of the box security. Using RBAC and encryption
• Total cost of usage is less than setting up in-house servers
• It is accessible from any where.. so no additional network setup is required.

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

• CodeArtifact does not support packages like debian. It will be nice to see them support that.
• Does not provide security scanning of the packages
• Lacks support for third party CI/CD toolchain like Jenkins

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

Very easy to use, great tutorials, documentation and cheat sheets out there to help you become a Docker Wiz

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

AWS CodeArtifact is an excellent choice for organization(s) which are looking to move their infrastructure and devops toolchain to Amazon. It is very useful for teams/organizations on limited budget or do not want to take on infrastructure and maintenance costs associated with the artifact repository. Other software solutions require resources for setting up and need ongoing maintenance.

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

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

• Overall CodeArtifact has positive ROI on the our team. We had limited budget for procurement of server/administrators. With CodeArtifact we were able to get some savings.
• We were able to deliver faster hence customers were quite happy. That led to customer satisfaction
• We didnt have to invest on maintaining network infrastructure/uptime and security. That saved us quite a bit of hassle and funds.

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.