Azure Container Registry Reviews

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.

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.

It has a geo-replication setup within the deployed region, and ACR provides resiliency in downtime in any specific zone. This results in faster image pull, significantly reducing the time to pull. ACR operates on the same Microsoft network; it doesn’t route through public networks, further enhancing speed.

I was working with SQL and in Azure DevOps. When the development team created the microservices, the microservices needed the connection with the SQL database. I used the SQL database to connect the microservices. The microservices were created by Java.

I used Azure Container Registry to send the Docker image to the Azure environment. I uploaded the image to Azure Container Registry to use in the AKS environment.

Azure Container Registry can be used to detect vulnerabilities in your image. If you have vulnerabilities in your code and when you build the Docker image, you can scan the image to find vulnerabilities.

The first impact is that you have a secure image. You don't have an image with vulnerabilities in your AKS cluster. It is the best practice to have a scanner in your container integration. You can use the container scanning to detect vulnerabilities when deploying the image.

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.

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.