Senior Cloud Engineer at a tech vendor with 1,001-5,000 employees
Real User
Top 20
Jan 19, 2025
The main use case is for deploying any standard application. I simply use Compute Engine, which is comparable to a virtual machine. It is essentially a VM machine.
I have worked with SAP migration. During SAP migration, we have different flexibility of the classes of compute for the load for SAP's load. My whole career was in SAP. So when I moved to cloud, I also did migration of SAP loads into the cloud.
I use the solution in my company for a website, specifically for some web applications. I just use Google Compute Engine as a server for my website and my web application.
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.
Network Engineer at a tech services company with 51-200 employees
Real User
Sep 20, 2023
We use it primarily for our testing. For example, if you want to deploy a laptop or something to test before deploying something on our appliance site. And we use GCP. I'm just using it for testing and lab deployment setups.
Google Compute Engine is the base and the fundamental part of the infrastructure as a product of the Google Cloud platform. Everything is based on the Compute Engine. We use Google Compute Engine to create instances and then use the instance to connect and integrate with other products on the platform. I'm a data scientist and I use Vertex AI a lot. Each Vertex AI has a fragment called Compute Engine. With Compute Engine, you can integrate the database and use Vertex AI with it.
We use GCE for deploying our applications, websites, web applications, and web services. It deploys our code into production. We use that instance for automated load handling, enabling horizontal scaling and load increases. About 30 to 40 people at my company use it.
We are using Google Compute Engine for deploying virtual machines for customers, as well as one or two internal uses. We use it mainly, as a managed service we offer customers.
Google Compute Engine provides scalable virtual machines for hosting applications and services with integration into Google's ecosystem. Offering cost-saving options and customizable machine configurations, it supports high availability, effective migration, and flexible resource allocation.Google Compute Engine stands out by offering seamless integration with Google services and cost-effective options such as Spot VMs and auto-scaling. With SSH access, customizable machine configurations,...
My usual use cases for Google Compute Engine involve deploying the backends and APIs only.
The main use case is for deploying any standard application. I simply use Compute Engine, which is comparable to a virtual machine. It is essentially a VM machine.
I have worked with SAP migration. During SAP migration, we have different flexibility of the classes of compute for the load for SAP's load. My whole career was in SAP. So when I moved to cloud, I also did migration of SAP loads into the cloud.
I use the solution in my company for a website, specifically for some web applications. I just use Google Compute Engine as a server for my website and my web application.
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.
We use it primarily for our testing. For example, if you want to deploy a laptop or something to test before deploying something on our appliance site. And we use GCP. I'm just using it for testing and lab deployment setups.
We use Google Compute Engine as a VM.
Google Compute Engine is the base and the fundamental part of the infrastructure as a product of the Google Cloud platform. Everything is based on the Compute Engine. We use Google Compute Engine to create instances and then use the instance to connect and integrate with other products on the platform. I'm a data scientist and I use Vertex AI a lot. Each Vertex AI has a fragment called Compute Engine. With Compute Engine, you can integrate the database and use Vertex AI with it.
We use the solution to host a self-hosted helpdesk.
We use GCE for deploying our applications, websites, web applications, and web services. It deploys our code into production. We use that instance for automated load handling, enabling horizontal scaling and load increases. About 30 to 40 people at my company use it.
We are using Google Compute Engine for deploying virtual machines for customers, as well as one or two internal uses. We use it mainly, as a managed service we offer customers.
This is a web application and deployment is moving to GCP for disaster recovery purposes .