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
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
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 ...
- Quay.io
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. ...
- Google Container Registry
It is a single place for your team to manage Docker images, perform vulnerability analysis, and decide who can access what with fine-grained access control. ...
- 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. ...
- Gandalf
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
- Uses a very familiar collaboration model as GitHub, the2
- Provides public and private repositories1
- 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...!
Which one to choose Docker Hub or Harbor for a startup that is starting its journey into Kubernetes
Kubernetes
- Leading docker container management solution164
- Simple and powerful128
- Open source106
- Backed by google76
- The right abstractions58
- Scale services25
- Replication controller20
- Permission managment11
- Supports autoscaling9
- Cheap8
- Simple8
- Self-healing6
- No cloud platform lock-in5
- Promotes modern/good infrascture practice5
- Open, powerful, stable5
- Reliable5
- Scalable4
- Quick cloud setup4
- Cloud Agnostic3
- Captain of Container Ship3
- A self healing environment with rich metadata3
- Runs on azure3
- Backed by Red Hat3
- Custom and extensibility3
- Sfg2
- Gke2
- Everything of CaaS2
- Golang2
- Easy setup2
- Expandable2
- Steep learning curve16
- Poor workflow for development15
- 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:
https://eng.uber.com/distributed-tracing/
(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)
Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark
Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.
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...
Harbor
- 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
We are operating a smart water purification plant called AAA. AAA has a Docker-based AI platform, and we want to build several water purification plants like this. In addition, it plans to create a headquarters that manages these water purification plants in an integrated way and build a big data platform there. Although I don't know if Ansible AWX can replace Harbor or Kubernetes among the three solutions above, I would like to know which solution is suitable for us and why. May your business go well...
Which one to choose Docker Hub or Harbor for a startup that is starting its journey into Kubernetes
- Great UI6
- API1
- Docker cloud repositories are public by default. Bad0
related Quay.io posts
related Google Container Registry posts
Amazon Elastic Container Registry Public
related Amazon Elastic Container Registry Public posts
- Scalability and replication of TB's in a second.3