Container registry technology is picking up steam with microservices architecture, with current Google trends indicating clear growth in this area. While there is no disagreement that a registry is needed; it is clear you need a robust one to deliver your container images to customers effectively. We should, however, set what our expectations should be when working with a container registry. Here are ten things to look for in a container registry.
You may also enjoy: Container Registries — A Battle Royale
1. Consumer-Centricity
When you create a container image, you definitely need a registry so your consumers can effectively consume both the first version, as well as subsequent versions. With continuous image updates, customers must be notified of the new versions so they can easily pull these new images in an effective and seamless fashion.