Azure Container Registry Reviews

We used Docker, and we aren't using the typical monolith model. We've changed to the microservices model, so we first used Docker for every microservices and then deployed that to different types of clusters. For example, in West Europe, and then the US, etc. We needed help storing those images, so we used Azure Container Registry for image and artifact storage when deploying to multi-regional clusters.

What I like best about Azure Container Registry is that it's fast. It also has 24 x 7 reliability. I didn't face any downtime issues using Azure Container Registry.

I also like how secure the solution is, especially as it's from Microsoft. Microsoft has very secure cloud services.

Azure Container Registry also provides role-based access, a very useful feature, so my team can't access the solution if it's pre-production.

I can say that Azure Container Registry has done an excellent job for the company.

The institution I work in intended to go with the Azure App Service with Docker containers, and Azure Container Registry fits the bill.

During the standard Azure DevOps pipeline, the institution built the container and then pushed the container directly to Azure Container Registry. Then, in the next stage of the same DevOps pipeline, the institution pulls the Docker image from the Azure App Service, which is already deployed to Azure Container Registry.

Overall, the Azure App Service posts the Docker images through its connection with the Azure Container Registry.

I'm working in a financial institution that has limitations to the type of service it can consume, even on the Azure cloud. There is a limited set of services, and Azure Container Registry is the only service approved by the security guy.

My main goal was to work independently from the container and the Azure App Service language that's already been predefined because when you deploy the application through the Azure App Service and you're working with REST API applications, there is a limited set of Java runtime compilers that can go and run on the Azure App Service, so the institution does not want to depend on the programming language from Microsoft. This is why the institution decided to go with containers, which is the only way forward.

With the Azure App Service and containers, Azure Container Registry is the only solution that can push and pull the Docker images because the configuration my institution has doesn't have access to the public internet, so my team cannot pull images randomly from different sources, even on-premise ones, so using Azure Container Registry is the only way the institution can inject images into the environment and resource groups.

The solution is really useful because whenever you want to deploy the containers, you need to have a place to store those container codes so that they can deploy easily. It is always better to store those codes in the solution itself so that you can deploy them through the pipelines. That is where Azure Container Registry comes into the picture. And also, it can duplicate to different zones and locations.

The most valuable feature is the zone replication and resiliency, because otherwise you have to build a system, and you need to worry about the resiliency and the backup of those codes. With this solution, you don't have to worry about all those things.

It's running behind a big financial and legal customer, who runs Service Fabric behind a front door, servicing local banking containers on an ISV solution developed internally.

The building of images on the container is quite cumbersome.

Our company uses the solution to store docker or other types of images for products and software that we are developing. We use the solution for its intended purpose and how most other companies use it.

We have some pipelines in Azure DevOps and we store images created through the pipelines in our registry. We use the registry for deployments. 

We work for a contractor who has thousands of projects. It is difficult to determine how many people use the solution because of the number of projects. It seems to be the trend with their projects to use the solution along with AK and Kubernetes clusters. Our specific team includes 15 people who use the solution quite often. 

Specific tokens can be used to set folder structure or restrict things like read or write access. 

The solution has good accessibility and is quite easy to understand. 

Configurations are quite simple. 

We predominantly use Azure Container Registry in our company for the deployment of secure images to ensure consistency.

Feature-wise, the security model and access controls are pretty straightforward and valuable.

The customers need a container system. In the old days, we used to have binary installations with classic delivery. Now, Azure Container Registry is something related to the packaging of the application. It allows us to package applications and run them anywhere using the application image.

The Azure Container Registry helps in scaling efficiently. In terms of scaling, it helps us deploy quickly from one server to additional servers within a fraction of a minute. It doesn't require the same time that was needed originally, allowing for rapid scaling.