Google Compute Engine

We use Google Compute Engine in a hybrid and multi-cloud solution. We find that using it for direct ad-hoc use cases meets all of our demands. We have attempted some more complex networking and multi-regional use cases but were not able to achieve satisfactory results. Google Compute Engine is extremely appropriate for anyone requiring quick, scalable, reliable infrastructure.

GCE is well suited for the following scenarios. GCE is very easy to use, and we can navigate on the console easily for trying various options. Reasonable pricing for the VMs help to reduce the overall budget. Recommendations for running VMs to scale up or down. Set of predefined VM types. Preemptible instances.

Google Compute Engine is suitable for any scenario that fits one of the pros I listed. It is very flexible and easily configurable. In many cases, VMs need to be spun up on the fly programmatically, and without orchestration software, one can accomplish this by using one of the APIs.

I have recommended the platform to students, friends and family members alike. The help and documentation is very easy to follow for a beginner. Plus, GCP has built in tools which make some common tasks that non-production level cloud users need to accomplish very easy in an automated way.

Now, to address the question of recommending GCE to a colleague, ultimately the organization will have to make a decision regarding the entire cloud platform. It wouldn't make much sense, outside of a special case, to use GCE for some parts of your cloud infrastructure and a competitor on other parts.

That practical caveat aside, I believe that the GCP brings a strong suite of tools to the table overall and is good value for money at this time as well.

Developer familiarity to certain competing platforms can be a sticking point, but a colleague who is already asking for a recommendation is likely already open minded about moving to GCP.

It is a stable service created by Google. The quality of service is good enough to create a full fledged production environment.

Google Compute Engine is particularly well suited for multi-environment testing, development, and experimentation with the low cost of spinning up small instances along with the speed at which it can be done. It also does well hosting small websites and proxy servers that don't see a lot of network traffic.

GCE is very well suited to small to mid scale deployments. It is also run very well with AI workloads especially when using Google TenserFlow et al. It is less appropriate for extremest scale deployments that spam multiple data center (probably because of lack of document on best practices)

Google Compute Engine is well suited for:

• All situations where one needs to allocate compute capability. Google Compute Engine offers a variety of server configuration and one should be able to find a matching configuration, except for largest servers or mainframes. This still may be the case for large relational databases in enterprises.

Google Compute Engine is less well suited for:

• Processing confidential information if the organization does not master security in cloud environments. One cannot simply transplant an application from a private data center to the cloud and expect the same security. Security needs to be designed and implemented from the start.
• Period workloads processing events. For that, consider Serverless/Function as a Service which is also a offering on Google Compute Platform.

In my opinion, most cloud applications should consider Google Compute Engine from a speed and pricing perspective. Of course, you should do an assessment based on what your application needs to do and how it needs to perform, but there's a machine for most kinds of deployments. If you have the expertise nearby, all the better.

Google Compute Engine offers you the possibility to scale your computing resources up or down quickly. Is a flexible solution that can be utilized by everyone who wants to manage software without having to worry about hardware. It's easy to create servers, and can connect to servers by RDP or SSH. It's a great choice for small and big organizations. We migrated all our critical servers from hardware to visualized servers and we reduced our cost significantly. It is more efficient to migrate you ERP to virtualization server to Google Compute Engine that on your hardware.

Google Cloud Compute Engine is well suited for companies doing advanced analytics, including machine learning and artificial intelligence. The software is less useful for smaller companies with only small data sets available for analysis. The software works well if you need instant access from anywhere in the world and if you are used to the Google infrastructure.

GCE is so customizable and extensible that it can fit most use cases and applications. Costs are excellent and it has become the most useful tool in our collection to deploy products, test scenarios, migrate workloads, and move out of the "server room". Ease of management cost control and customization are the biggest wins with GCE.

You can use Google’s web services to build a highly customized solution to meet all your company’s needs. Very easy to build, test, deploy and manage applications and services though their data centers. Google Compute Engine gives you the freedom to move away from having your servers based on premises which can reduce costs.

As any IaaS provider, Google Compute engine is suitable for any kind of companies, from small to large ones. You can easily create new servers and start configuring it in minutes. Usually, the prices are lower when comparing with buying a local server. Furthermore, Google Compute Engine is integrated with other services from Google Cloud platform.

Google Compute Engine is very similar to AWS EC2, and in most of the same regions, but also in a couple of additional geographic locations. So if proximity is crucial, there are some additional options with GCE over AWS EC2.

Suited: Compute Engine is really good for any monolith type services which you need to host a service globally. And it works very well. Not Suited: autoscaled services that have long/heavy post-processing activity during termination.

For companies that require GPU-accelerated instances, GCE may be your only good option. They offer a lot of services that aren't available at the next best cloud computing platform (in my opinion), DigitalOcean. Beyond the functionality, the UI and documentation can be approved a lot, but if you're used to the way Google designs their developer tools and APIs, then you're probably all set with moving forward with Google's Compute Engine.

Small businesses can easily scale their applications with little up front cost in setting up the infrastructure for their application.

We are a web software company and GCE has been great for hosting our web applications. We have a single-node and multi-node instances and GCE never misses a beat. We also have some Windows Server clients, so launching and testing our software in Windows is made possible by GCE. When comes to reliably hosting web infrastructure at scale, GCE is a fantastic choice.

If anyone, especially developers, whom are a newbie, they can quickly launch pre-built servers with desired applications easily. The projects come with the git repository that can rapidly be installed with a few single clicks.

Compute Engine provides VMs which you have to maintain by yourself, but you can run anything you want in there. Consider using App Engine for web sites, Container Engine for anything that needs to be often deployed and scaled automatically (if it doesn't fit into App Engine). On Compute Engine you can easily spawn up an instance with hundred GB of memory, do your stuff, and shut it down after couple of hours. You will only pay for what you used. But be careful -- there's some people who "forget" about running instances and then they are surprised with huge bills in the end of the month -- this is your responsibility to turn them off, since Google will do their part to make sure they are working flawlessly without any downtime.

GCE is well suited for building scalable tools in the cloud. If you have an on demand service, GCE is a great tool for spinning up and down servers quickly. GCE can get expensive for full time applications using high network throughput. If you have a lot of data moving between servers, make sure you understand the cost associated with how information will be flowing over the network.

Google Compute Engine is really great for web-based software that needs high availability and flexibility in scaling. I wouldn't necessarily recommend it for simple website hosting under most circumstances as the bandwidth can get expensive quickly if serving large files, but even for that it's very reliable and easy to set up and get started.

I would recommend Google Compute Engine for companies with adept engineering teams that want to maximize the value of their talent and focus on the core strengths of their business (product, R&D, research, UX), rather than waste resources on infrastructure. The engineering team should have good knowledge of the tools available and how to stitch them together into a scalable product.

If running a Kubernetes or any container engine environment, Google Compute is simply the best. Given that Kubernetes and containers in general are still fairly new in terms of widespread usage, there are hangups, but those seem to exist in any hosting platform. Google's terminology, as compared to Azure and AWS is also really easy to understand. If you want logging, it's called logging. If you want storage it's called storage. Where Google Compute falls short is the same as where all cloud providers fall short: if you want high resource systems that are always online, it will get expensive really quickly.