Amazon Elastic Container Service (Amazon ECS) vs. Google Container Registry

Amazon ECS is well suited for the scenarios where you want to deploy a microservice to a cloud and instead of manually specifying instance size, number of instances and then specifying the configurations and connecting it with other cloud services like database service, secret manager service etc., you just want to specify these configurations as a file and using that file, the ECS would deploy the service and keep it healthy. It might be less suited for a scenario when you don't want to stick to AWS specific solution for your microservice deployment. The ECS configuration file is specific to AWS ECS and may not be useful for other cloud providers like Azure etc.

Incentivized

As a Cloud Engineer while working on a migration project we used GCR and my experience of using it is actually good the reason behind this is: 1: GCR uses industry-standard encryption to protect your data.2: GCR offers data loss prevention features to help you prevent sensitive data from being leaked or exposed and last but not the least is GCR provides audit logging so you can track who has accessed your data and when, because of these reasons its my go to tool.

Incentivized

• One of the biggest advantages is the flexibility to change underlying EC2 instances. As the traffic or demand increases, we can easily change EC2 instances without any issues.
• Amazon ECS APIs are extremely robust and one can start and stop containers by firing one post request only. So, it is not mandatory to keep the demo solutions up for every time. Just at the time of demo fire the command - make the container up and running - do the demo - down the container with API. A simple portal can control every container which helps non-technical (sales, marketing) to do the demo without keeping the solutions up for the entire time frame.

Incentivized

• Object Immutability feature allows us to protect our code and backups from accidental or malicious changes.
• Data loss prevention feature helps us to prevent sensitive data from being leaked or exposed.
• GCR has support for machine learning which is in my opinion is best .

Incentivized

• Another AWS Service - While AWS has a service for just about everything, that is also a negative point. There is no service that does 4 out of 4 things you need. This service does 3 out of 4, another service does the fourth thing you need and another two things that the other service does.
• With AWS things in general, it's really hard to remain cloud agnostic. Keep that in mind.

Incentivized

• The one area which i think GCR lacks is that it currently supports a limited number of file types
• The major flaw a felt while working on it is it does not have feature of object versioning and object locking

Incentivized

Aside from some ECS-specific terms to learn at first, learning & starting to use ECS is relatively straightforward. AWS docs on the topic are also of high quality, with sound & relevant examples to follow. Troubleshooting container issues is also a breeze thanks to CloudWatch integration & helpful error messages on the AWS console.

Incentivized

Support is relatively good, although the documentation sometimes is lacking, as well as outdated in our experience, especially when we initiated the process of using this service. But once we found how to assemble things, we haven't really required support from anyone at AWS, the service works without problems so we haven't had the need to contact support, which speaks well of how ECS is built.

Incentivized

I chose Amazon ECS over Amazon EKS and other products because the whole infrastructure was decided to be designed on AWS cloud and Amazon ECS made it easier to make the clusters live in just a few minutes. Amazon ECS has better integration with other AWS services and we don't have to look for plugins to do the things, everything is available and can be configured from the AWS console.

Incentivized

It is very easy to integrate GCR with other services and I integrated GCR with GKE and Cloud Build. 1: While working on one project I created one pipeline pulls the app's Docker image from GCR and builds the app's Docker image. Deployed that apps image in GKE. 2: Ive stored the data in GCR and that data was being used by cloud Run applications

Incentivized

• Easy to manage as it has an orchestrator to manage the containers.
• Less costs and more flexibility with Fargate.
• Negative (tied to AWS, so could not easily integrate other tools like running a Redis cluster. Still, it works but not easily like Kubernetes.

• As a DevOps Engineer , GCR has made a important contribution to my organisation because GCR can be used to store code and assets, which can help to reduce the development time for new projects.
• Using GCR has bee­n a cost-effective solution for us since­ we only pay for the storage we­ actually utilise. This has resulted in significant savings on our cloud storage­ expenses.
• We trust GCR be­cause they prioritise the­ security of our data by utilising industry-standard encryption. This assurance brings us pe­ace of mind, as we know our information is protecte­d.

Incentivized