What is Amazon ECR and what are its top alternatives?
Top Alternatives to Amazon ECR
- Docker Hub
It is the world's easiest way to create, manage, and deliver your teams' container applications. It is the perfect home for your teams' applications. ...
Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions. ...
Harbor is an open source cloud native registry that stores, signs, and scans container images for vulnerabilities. Harbor solves common challenges by delivering trust, compliance, performance, and interoperability. It fills a gap for organ ...
Simply upload your Dockerfile (and any additional files it needs) and we'll build your Dockerfile into an image and push it to your repository. ...
- Amazon Elastic Container Registry Public
It is a fully managed registry that makes it easy for a developer to publicly share container software worldwide for anyone to download. Anyone (with or without an AWS account) can use it to pull container software for use. Amazon ECR Public Gallery is a website that allows anyone to browse and search for public container images, view developer-provided details, and see pull commands. Developers no longer need to use different private and public registries when building and sharing their public container artifacts. ...
- Kraken by Uber
A P2P-powered Docker registry that focuses on scalability and availability. It is designed for Docker image management, replication and distribution in a hybrid cloud environment. ...
We provide a secure private registry where users can host their docker images and share them privately and securely within teams. ...
Amazon ECR alternatives & related posts
- Provides public and private repositories1
- Uses a very familiar collaboration model as GitHub, the1
- Quickly creates organizations, add users or create grou1
- Allows users to set permissions to restrict access or s1
- Fairly inexpensive with usage based pricing1
- Security scanning available1
- Lacks fine grain access control1
- Does not provide any insight into the registry usage1
- Lacks LDAP, SAML and OAuth support1
related Docker Hub posts
We have been using Docker Hub free plan for some time, which had automated builds feature included in the free plan. Recently it has been removed from the free plan. Therefore we have thought to either go ahead with a paid plan of Docker Hub, which includes automated builds feature or migrate to use Amazon ECR as the container registry management solution. Since we already use some AWS services, going ahead with Amazon ECR is a viable solution. I am a bit confused as to what would be the best choice going ahead. Please advice...!
- Leading docker container management solution162
- Simple and powerful126
- Open source104
- Backed by google75
- The right abstractions56
- Scale services24
- Replication controller19
- Permission managment10
- Supports autoscaling7
- No cloud platform lock-in4
- Quick cloud setup3
- Open, powerful, stable3
- Promotes modern/good infrascture practice3
- Captain of Container Ship2
- A self healing environment with rich metadata2
- Cloud Agnostic2
- Runs on azure2
- Backed by Red Hat2
- Custom and extensibility2
- Easy setup1
- Everything of CaaS1
- Poor workflow for development15
- Steep learning curve15
- Orchestrates only infrastructure8
- High resource requirements for on-prem clusters4
- Too heavy for simple systems2
- Additional vendor lock-in (Docker)1
- More moving parts to secure1
- Additional Technology Overhead1
related Kubernetes posts
How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:
Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.
Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:
Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.
After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...
- Good on-premises container registry4
- Container Replication1
- Nice UI1
- Vulnerability Scanner1
- Supports LDAP/Active Directory1
- Supports OIDC1
- Support multiple authentication methods1
- Perfect for Teams and Organizations1
related Harbor posts
- Great UI6
- Docker cloud repositories are public by default. Bad0
related Quay.io posts
related Amazon Elastic Container Registry Public posts
- Scalability and replication of TB's in a second.3