The deployment procedure is quite straightforward.

You have an account, and then you search the account engine. Then you can see the dashboard, create an instance you need, and choose the engine you want to use. You can also choose the storage disk you want to attach with it. This will give you the highest flexibility and you can choose the network you want to integrate with. You do not have to customize it because it also has a default mode which helps you finish the basic settings.

It does not require much maintenance. You can maintain it yourself. For example, our former employee left the company but his computer engine was quite large and cost a lot of money. I downgraded the engine myself and switched to a smaller instance. That saved us around sixty percent of the cost. This just goes to show that you can do almost anything you want with the solution.

Depending upon the deployment's complexity, customers with fewer workloads choose a manual deployment. But what we recommend is an automated way. Before deploying workloads on the Google environment, we must build the landing zone and other things. Google has a very good support structure, with many Terraform scripts and code, which can be used to quickly deploy a landing zone. This landing zone platform port is customizable depending on the customer's requirement. We use Terraform codes to deploy the entire landing zone and even the deployment of the VMs. The workload is typically automated.

It defeats the purpose of going onto the cloud when we want a single person to sit and deploy the entire thing. Even though it is much faster when compared to the on-prem version. Very large deployments with more than 100 customers using 500 to 1,000 VMs typically have to be automated. Still, it's not only about deployment but also the maintenance of all these workloads. For example, whichever OS is deployed on the VMs, we have to patch those systems regularly whenever there is some security patch or any patch that comes in. And unless we have an automated solution, we cannot do it manually because it takes a lot of time. But in the Google Cloud case, we have something called a VM Manager, and we can configure this VM Manager to automatically deploy these OS patches onto the VMs. The deployment and maintenance of all the Google Cloud Compute Engine instances are automated.

It takes less than five minutes to deploy the solution.

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.

Google Compute Engine's installation is basic. 

In terms of the deployment process, we have two major deployment processes. One is via the console; the other is via the command line interface. And the third is using any Terraform tools like Terraform modules. So I've used all three of them. 

Personally, I'm comfortable with all three. Terraform requires some upskilling and some learning curve. However, the console is quite straightforward to implement and use, as well as the command line interface. So, specifically, using the shell, like, a piece of cake.

The initial setup is very easy. The deployment took two minutes to complete.

Setting up GCE is straightforward. It usually takes less than a minute to spin up an instance. 

The initial setup of Google Compute Engine is easy. All the setups are straightforward. All the public cloud tools are now offering a simplified solution. The whole process of deployment can take a few minutes. In most cases, it will take under one hour if there are more virtual machines being installed.

The steps taken for the deployment are simple. We only need an account. Once we have an account, we will have access to the cloud console. There are two options for deployment, using the GUI or the console. Both are easy to use, we only need to open a few ports to keep the machine running and active.

I rate the initial setup of Google Compute Engine a nine out of ten.

Two people are enough to handle the tool's deployment. The deployment takes one hour to complete. 

Yes, the initial setup is very straightforward because the Datalab kernel is installed on a virtual machine in the cloud rather than on your local machine. In addition, the quick start documentation was very easy to follow. Google Cloud Datalab is installed using Google Cloud Shell which is accessible from a web browser which means that you can have access to the full Google Cloud Datalab user interface from a light-weight laptop such as a Chromebook.

The initial setup is pretty straightforward. 

The initial setup is reasonably straightforward.

The existing environment is fairly flat and static.