What is our primary use case?
Compute Engine is an option to create virtual machines in GCP. We can set up our service now. We can use Compute Engine for load balancing, and we can categorize it into three different types: general purpose, compute optimized, and memory-optimized. There are a lot of CPU options to choose from, so we can select the one that best suits our needs. We can create Compute Engine instances anywhere in the world, and we can deploy our services to them. This ensures that our application has a global presence.
Another feature of Compute Engine is its networking capability. It provides networking capability to VPCs, which are private cloud networks. Compute Engine also provides instance templates. We can define our virtual machine configuration in an instance template and then use that template to create new virtual machines. We don't need to specify the region or other details when we create an instance template because instance templates are global services. We can use an instance template to create a new virtual machine at any time with the same configuration.
Another service provided by Compute Engine is managed instances. It allows us to create a group of identical virtual machines. The virtual machines in a managed instance group all have the same configuration. We can ensure that a minimum number of instances are always up and running, and if an instance fails, Compute Engine will automatically create a new instance with the same configuration. This ensures that our service is never unavailable.
Compute Engine also provides a load balancer to distribute traffic to our virtual machines. The load balancer provides a single IP address for our service, and it distributes traffic to the virtual machines in our managed instance group. This allows us to scale our service up or down without having to change any client code.
What is most valuable?
It's the managed instance. You never feel any delay or service. If something happens, it will automatically create a new instance with the same configuration.
What needs improvement?
It would be better if there was an option to change the background. Like in Gmail, there's an option to change your theme. That's my recommendation.
For how long have I used the solution?
I started learning about this solution last year.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
It is a scalable solution. Google is trying to make data centers and edge locations to increase its services. Google provides machine learning and artificial intelligence through GCP.
Which solution did I use previously and why did I switch?
I used to try AWS EC2. It's a kind of infrastructure. I tried AWS EC2 before I learned EC2. It is helpful to learn GCP. EC2 is also the same. We can create virtual machines in the AWS platform.
When it comes to the purpose perspective of end users, GCP is much better than AWS, especially for building devices. Also, the network device is very simple. When we create a VM, it is better. When we create resources, like databases, I will definitely go with GCP. And when I compare, I really go with GCP. It is very easy to use and have minimal learning curve.
How was the initial setup?
Everything is simple and useful. The initial setup is not challenging. You just need a credit card and a Gmail account. If you have a credit card, you can just get a platform account.
Google is providing money for learning Google Compute Engine. They offer a $300 free trial to new customers. Any beginner can easily get started.
From the maintenance point of view of Compute Engine, there is an option to auto-cost maintenance. So we never experience a delay in our services because our new build to host machines. There is no delay in that case. Nowadays, if something happens in Google Cloud, in case of numbers or necessary traffic, it will be resolved within a day or two.
What other advice do I have?
First of all, you have to analyze your workload and sign which kind of machine type, how much memory you need, and what kind of traffic you expect. Analyze your workload and your requirements. Make a cost explanation of how much you can spend for your service in a month.
Once you analyze your workload and determine your cost explanation, use the pricing estimation with the price target. And because you are the amount you plan to spend in a month. Find the cost provided by the price package. Compare both. If there is a minor or no difference, both are comparable. Everything is matching, you can go with your requirements and build your infrastructure based on your economy.
If there is a huge difference, you can reassess your resources in pricing guidelines and make resource changes. But the things you have to come there. If there is no significant difference, you can proceed. Otherwise, change the option.
And then you will get a solution, how to make both things like we've both things, like the infrastructure, it's preferred in your pricing estimation, and your actual costs. If both are almost similar, you can create it, use it, and deploy it.
Overall, I would rate the solution a nine out of ten.