Shulou(Shulou.com)06/01 Report--

This article mainly explains "what are the differences between AWS, Azure and GCE". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what are the differences between AWS, Azure and GCE".

More and more enterprises use container technology to deploy cloud applications. It seems that the relationship between container and cloud is getting closer and closer. So the big three cloud providers-- Amazon Web Services, Microsoft Azure and Google Industries-- have all launched their own container services. However, these services are not exactly the same.

For the purpose of this article, Cloud Technology Partners, a Boston-based cloud computing consulting firm, deeply analyzed Amazon Web Services (AWS), Google, and Azure container services, and carefully considered the use cases. The company carefully examined features that need to be focused on when evaluating or using cloud-based container services, including data management, scalability, performance, security, DevOps, and integration with management operations (see Table 1). Use cases cover development and operations and, in short, the features that must be used when you build and deploy applications using these three technologies.

Compare the scores of on-demand container products of the three major cloud providers.

On a score of 1-5, 1 is the lowest score and 5 is the highest score. A score of 1 means that the technology does not provide support for the item at all, while 5 means that the technology meets most of the feature and functional requirements of the item. The requirement examined in the DevOps item is that the container subsystem supports DevOps operations and maintenance, or provides the ability to integrate repositories. This article provides some basics for enterprises that are evaluating Google, AWS, or Azure container services. But the specific requirements of your own application are the most important factors driving the final product decision.

Integration and data consideration

Azure Container Service (ACS) is based on Apache Mesos, an open source container orchestration system. This means that thanks to the good reputation of the predecessor of ACS, the features and functions of Mesos, users can think that the features and functions of ACS are good. ACS, which is not fully available, is the latest of the container services mentioned earlier. With the further development of Microsoft container products, we will get more data, and many scores may change accordingly. Google is not much ahead, and AWS and Microsoft may catch up quickly. In AWS EC2 Container Service (ECS), we can see some operation and maintenance problems, such as the lack of fine-grained monitoring of containers. When considering the integration capabilities of ECS, management and operation and maintenance, it should be as powerful as other AWS products. Compared with the 5 points of Google Container engine (GKE), we have to give only 4 points. However, ECS does include CloudWatch integration, which is an advantage over ACS. In addition, for now, ACS only supports Linux containers. Windows support is almost ready, and Microsoft introduces Mesos,.NET developers who cannot use this service for the time being. From a data perspective, all of these services provide native data links without forcing the use of external API--, but there is room for improvement. A big concern is that they will bind native data services and containers together and do not provide open data access, which will enhance portability. If the data is tightly coupled to the container, it is difficult to create a portable container. This is an emerging field and we will continue to pay attention to it.

AWS, Google, and Azure container security

When security is considered, we find that Google's service, through its Kubernetes container choreography system, has a "secret" function and some additional resource restrictions that the other two services do not have. As a result, GKE scores highest in terms of security. Keep in mind that Microsoft also uses Kubernetes, but in a different way. Most of the content of this technology is abstract to the user. However, when looking at managed platforms, or public cloud platforms where container services run, it is interesting that the Google platform lags slightly behind AWS or Azure when it comes to security. Although Google works with third-party authenticated access management (IAM) tools, it lacks support for native IAM. Although this does not affect the score in the table above, it is also an aspect to consider when deciding which platform to use.

DevOps and scalability

When considering DevOps, both GKE and Amazon ECS have their own registry, but the Azure container service does not. Google and AWS provide better DevOps integration when considering container services on their respective clouds. Extensibility requirements are relevant to your application requirements, so we have to make assumptions based on the mechanisms they can provide, such as Mesos, and some of the use cases we see in the project. When examining the techniques used to host and run containers, you can use the same solution. For example, ACS using Mesos should provide decent scalability, but not as good as GKE, and GKE can provide better clustering capabilities. As we all know, Amazon ECS can provide high-quality scalability, which mainly depends on the highly scalable platform features that AWS brings to its container engine. To sum up, Google products are generally more advanced thanks to the tight integration of Google products and their own Kubernetes container clusters, as well as the development and operation support of Google. But Google is not much ahead, and AWS and Microsoft may catch up quickly. Based on AWS's market share, it is likely to provide a better container solution in the near future.

Thank you for your reading, the above is the content of "what is the difference between AWS, Azure and GCE". After the study of this article, I believe you have a deeper understanding of the difference between AWS, Azure and GCE, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.