.png)
Easier scaling and resource management
Distributed storage for high data redundancy
State-of-the-art network for faster sites
Multiple opportunities for new data center locations
Google lets you create custom machine types with any CPU/memory configuration. They let you opt for cheaper, Preemptible price instances with a single click.
Google connects each and every VM to its super-fast, low-latency networking. Amazon requires you to buy expensive 10G-capable instances and/or enable enhanced networking.
Google lets you set up simple Firewall rules. Amazon gives you VPC, security groups, network access control lists.
Google bills by the minute (not hour) and apply AUTOMATIC DISCOUNTS for long-running workloads, with absolutely no reserved pricing.
In AWS, the compute service is called “Elastic Compute Cloud” (EC2). The virtual servers are called “Instances”.
In GCP, the service is referred to as “Google Compute Engine” (GCE). The servers are also called “instances”.
A notable difference in terminology are GCP's; there are “preemptible” and non-preemptible instances. Non-preemptible instances are the same as AWS “on demand” instances.
Preemptible instances are similar to AWS “spot” instances, in that they are a lot less expensive, but can be preempted with little or no notice. GCP preemptible instances can be stopped without being terminated. In November 2017, AWS introduced a similar feature with spot instance hibernation. Flocks of these instances spun up from a snapshot according to scaling rules are called “auto scaling groups” in AWS.
The similar concept can be created within GCP using “instance groups”. However, instance groups are really more of a “stack”, which are created using an “instance group template”. As such, they are more closely related to AWS CloudFormation stacks.
Free tier – inexpensive, burst performance (t3 family)
General purpose (m4/m5 family)
Compute optimized (c5 family)
GPU instances (p3 family)
FPGA instances (f1 family)
Memory optimized (x1, r5 family)
Storage optimized (i3, d2, h1 family)
Free tier – inexpensive, burst performance (t3 family)
Standard, shared core (n1-standard family)
High memory (n1-highmem family)
High CPU (n1-highCPU family)
We have been using AWS for almost an year , running an EC2 instance ubuntu server type.In order to host an web application we need proper SSL and High Speed so we opted for LoadBalancing and SSL from AWS certificates.
In order to have SSL on our application we need to either use LoadBalancing or CloudFront.
Until free tier the AWS is good, but after free tier we found billing is getting higher and higher.
Now we went to google cloud compute engine to set up an instance ,as google cloud consists of auto scaling and load balancing by default there is no need of load balancer separately .
We are getting charged $5 with 30GB storage on GoogleCloud almost $15 saved from AWS Engine.
Google CLoud Performance is 1.5x faster than AWS Instances .