Akamai Cloud Computing (formerly Linode) include scalable and accessible Linux cloud solutions and services. These products and services support developers and enterprises as they build, deploy, secure, and scale applications.
$5
per month
Google App Engine
Score 8.2 out of 10
N/A
Google App Engine is Google Cloud's platform-as-a-service offering. It features pay-per-use pricing and support for a broad array of programming languages.
$0.05
Per Hour Per Instance
Google Compute Engine
Score 8.7 out of 10
N/A
Google Compute Engine is an infrastructure-as-a-service (IaaS) product from Google Cloud. It provides virtual machines with carbon-neutral infrastructure which run on the same data centers that Google itself uses.
$0
per month GB
Pricing
Akamai Cloud Computing
Google App Engine
Google Compute Engine
Editions & Modules
No answers on this topic
Starting Price
$0.05
Per Hour Per Instance
Max Price
$0.30
Per Hour Per Instance
Preemptible Price - Predefined Memory
0.000892 / GB
Hour
Three-year commitment price - Predefined Memory
$0.001907 / GB
Hour
One-year commitment price - Predefined Memory
$0.002669 / GB
Hour
On-demand price - Predefined Memory
$0.004237 / GB
Hour
Preemptible Price - Predefined vCPUs
0.006655 / vCPU
Hour
Three-year commitment price - Predefined vCPUS
$0.014225 / CPU
Hour
One-year commitment price - Predefined vCPUS
$0.019915 / vCPU
Hour
On-demand price - Predefined vCPUS
$0.031611 / vCPU
Hour
Offerings
Pricing Offerings
Akamai Cloud Computing
Google App Engine
Google Compute Engine
Free Trial
Yes
No
Yes
Free/Freemium Version
No
Yes
Yes
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
Optional
No setup fee
No setup fee
Additional Details
CPU, transfer, storage, and RAM are bundled into one price. Storage capacity can be increased with additional Block Storage or S3-compatible Object Storage. Instant Backups can be added with complete independence to the stack. Linode NodeBalancers ensure applications are available.
—
Prices vary according to region (i.e US central, east, & west time zones). Google Compute Engine also offers a discounted rate for a 1 & 3 year commitment.
More Pricing Information
Community Pulse
Akamai Cloud Computing
Google App Engine
Google Compute Engine
Considered Multiple Products
Akamai Cloud Computing
Verified User
Project Manager
Chose Akamai Cloud Computing
We built some applications on Google App Engine, and in comparison to Linode, you are more locked in and there is a steeper learning curve, as you have to adapt to Google's tools. In Linode, you can use whatever you are used to. With AWS, you are able to make whatever setup you …
Linode has been intutive to use. It is easier to find things. Billing is easier to keep track off and it is cheaper then others. Linode VM's are faster then the others.
Linode ticks almost all the checkboxes you need to host modern applications and systems. Price, scalability and customer service is the main reason for me to use Linode. We use Google Cloud and Azure for certain things, but when it comes to VPS Linode is way better. We have …
Information Technology Specialist, Digital Strategist
Chose Akamai Cloud Computing
There are a lot of very good cloud operations. Linode, for us represents a good offering. It offers a simple way to control infrastructure, without being overly simplified. For us, it was a good median giving us the flexibility to explore, experiment and still build for scale. …
I am still evaluating DigitalOcean Droplets as their pricepoint has moved more towards Linode, but so far I am leaning back towards Linode. They also don't have the GPU machines. But they do have a wider range of options for CPU. At present if you do lscpu on Linode it lists …
Verified User
Team Lead
Chose Akamai Cloud Computing
Linode often offers the most competitive pricing on regular usage.
Linode provides easier and more understandable pricing and value. I never have to wonder or estimate the month's costs or have any surprises. Linode also is more logically laid out and easy to get things set up and running quickly.
DigitalOcean had very bad communication both internally and externally. Vultr had good features but could not answer questions about Spectre/Meltdown with any specificity. EC2 and GCE's unpredictable costs and higher bandwidth fees make them annoying or expensive for most of my …
Though I have used DigitalOcean and also had a generally positive experience using them, I disliked that the IPv4 addresses given to me when using D.O. almost always failed MX blacklist checks and required me to intervene on my own to get them delisted. Because I have not …
Google Computer Engine: it is too expensive. You have to pay for computing resources (CPU, memory), storage, network traffic individually. While the quality of service is good, it's still with the same level of Linode.
For simple VMs or Kubernetes, Linode is cheaper and it also has consistently good performance. As long as this is what you need, you get all you'd want. AWS and GCP shine when you need their other services. Oracle Cloud was bare bone and expensive. Droplets are easy to start …
Red Hat OpenShift was the first product I used and it was fantastic--until they changed to a container model and kicked everyone of the previous model. From there I moved to Linode and haven't looked back. You have much more control but it does mean you need to keep on top of a …
Compared to the "big three" cloud providers, Linode does not have the enormous range of service offerings that they do. I would not attempt to build the next Instagram on Linode. But for companies that simply want a straight-forward cloud provider, they're definitely our …
One of our clients was previously hosted on Rackspace, then Google Cloud Services. Their Rackspace services were very expensive and provided little in the way of migration or management. After re-engineering their deployment, we migrated them to Google Cloud Services (GCS) …
Linode is competitively priced, but more importantly its management interface is fantastic. Over the past seven years, I have seen firsthand the deep expertise behind the decisions they make in both their physical layers (data centers) and software stacks.
We have considered both AWS and Google Cloud. We are sticking with Linode because we're comfortable administering our systems and don't need the global scale (and corresponding cost) of the bigger cloud platforms. As noted previously, Linode is a great solution for …
App Engine is a much more streamlined system than EC2. There is a fundamental difference between them, but they are used for basically the same thing as far a I could tell -- to serve applications EC2 is certainly more complicated, but if offers more machine-level control if …
It's the manageability of the Google App Engine which made it a better option in our case. It's quite straightforward to deploy on App-Engine. No worries for monitoring setup
We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as …
You can spawn up your own cluster using Kubernetes or Container Engine which will scale automatically when configured properly, but you have to keep an eye on that cluster. In App Engine you don't have to worry about it at all, just ship your code and it will run.
RunMyProcess is a good solution if you have a relatively straight forward workflow application. However, this solution charges for every page load of the application. If you have a large enterprise customer, these costs can quickly jump if thousands of people are accessing the …
Google App Engine is slower in comparison, and costs more than Google Compute Engine. We chose Google Compute Engine because Google App Engine was way too slow (mainly due to having to use Google Cloud Storage).
The perfect blend of setup flexibility, costing and trust of Google could be my answer to the comparison. This being a server backed service so, ruling out the functions. The Setup flexibility and speed set the GCE apart from Kubernetes. Compliance, regulation and the security …
Google Compute Engine provides on-demand computing resources that are easy to scale up or down according to my organization needs. This allows our business to quickly adapt to changes in demand without having to invest in additional hardware. It also offers a very competitive …
Google App Engine is a platform as a service where everything is taken care of by Google and we just need to write the code and deploy it onto it. But we hardly have much control over the VMs and the OS offering is not much. We had a limited amount of OS version supported. …
We have used a few other cloud providers of similar services and continue to use Google Compute Engine because it fits well within our technology stack and is cost-effective while providing the service we need. It has allowed us to use and experiment with many more …
We have used Amazon in the past. GCE has come such a long way since then, we have not looked back. IAM and access are on par, cost management is slightly better on GCE. Where we have really seen improvements are the VM types (GCE allows for deep customization that does not …
App Engine is somewhat similar, but we use it together with Compute Engine. App Engine is good for serving end requests to users -- it can scale automatically to any number of requests, but has it's own limitations. Compute Engine does not have any limitations. but you have to …
Akamai Connected Cloud Linode would be a good service to host a content delivery network (CDN) because of its edge network but I'd prefer not to use Akamai Connected Cloud Linode for tasks that need GPU power such as Machine Learning or Artificial Intelligence (AI) because Akamai Connected Cloud Linode lacks deep GPU compute compared to AWS or Google Cloud or Microsoft Azure
App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.
You can use Google Cloud Compute Engine as an option to configure your Gitlab, GitHub, and Azure DevOps self-hosted runners. This allows full control and management of your runners rather than using the default runners, which you cannot manage. Additionally, they can be used as a workspace, which you can provide to the employees, where they can test their workloads or use them as a local host and then deploy to the actual production-grade instance.
Scaling - whether it's traffic spikes or just steady growth, Google Compute Engine's auto-scaling makes sure we've got the compute power we need without any manual juggling acts
Load balancing - Keeping things smooth with that load balancing across multiple VMs, so our users don't have to deal with slow load times or downtime even when things get crazy busy
Customizability - Mix and match configs for CPU, RAM, storage and whatnot to suit our specific app needs
There is a slight learning curve to getting used to code on Google App Engine.
Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)
I've been with them a long time. They provide me with the capabilities I need coupled with knowledgeable support that's not pay-for-extra. However, if I move to a non-Linux OS, the level of support by necessity will drop off. I can still ask questions about the infrastructure but I my ability to ask about OS features will decrease.
App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.
Its pretty good, easy and good performance. Also, interface is very good for starters compared to competitors. Infra as Code (IaC) using Terraform even added easiness for creation, management and deletion of compute Virtual Machines (VM). Overall, very good and very easy cloud based compute platform which simplified infrastructure, very much recommend.
Simple and clear, no BS interface. From a design perspective it's no Apple or Stripe, but it does what it needs without making me want to stick a fork in my eyes, like when being forced to use Azure, AWS or GCP.
I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster
Having interacted with several cloud services, GCE stands out to me as more usable than most. The naming and locating of features is a little more intuitive than most I've interacted with, and hinting is also quite helpful. Getting staff up to speed has proven to be overall less painful than others.
There is very little planned downtime. Whenever planned downtime is necessary I'm always given lots of advanced notice and an explanation that I can pass along to my users that they'll understand. I really appreciate that Linode appreciates my commitment to reliable service to my users. It shows that they believe they've been successful when I'm successful.
Google Compute Engine works well for cloud project with lesser geographical audience. It sometimes gives error while everything is set up perfectly. We also keep on check any updates available because that's one reason of site getting down. Google Compute Engine is ultimately a top solution to build an app and publish it online within a few minutes
Servers are well dimensioned and price performant. Of course one always wants more, so if they were to upgrade their hardware for the same price I'd consider moving more workloads. Networking - never had an issue. Hardware speeds - disks are fast and can grow to great size.
It works great all the time except for occasional issues, but overall, I am very happy with the performance. It delivers on the promise it makes and as per the SLAs provided. Networking is great with a premium network, and AZs are also widespread across geographies. Overall, it is a great infra item to have, which you can scale as you want.
Support was excellent and fast. The documentation is extensive and helpful. I learned many things from their online documentation. I did not contact them by phone, but email took a day or less. Complex problems would probably need a service contract. I liked the friendly and polite tone of the support.
Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.
The documentation needs to be better for intermediate users - There are first steps that one can easily follow, but after that, the documentation is often spotty or not in a form where one can follow the steps and accomplish the task. Also, the documentation and the product often go out of sync, where the commands from the documentation do not work with the current version of the product.
Google support was great and their presence on site was very helpful in dealing with various issues.
We got kick started with an initial walkthrough along with some free credits. The initial walkthrough helped us to understand Linode's ecosystem and start our hands on with Linode. We tried out some apps from Marketplace initially with the free credits, which not only helped us understand Linode better, but also those apps. We had implemented many such apps to our customers with Linode
We're a small organization. The implementation of our Linode solution was trivial. Once I justified a cloud server to my bosses over a co-location -- the co-lo wasn't as fast as our linode server in load tests -- it was a matter of moving one Linux implementation to another. Trivial.
We switched to Linode from Namecheap due to poor uptime, and never had any issues with stability ever again after switching. We also cut our costs in half by switching. We compared Linode to DigitalOcean and Vultr, with the primary factor that caused us to go with Linode initially being their documentation. After using Linode for 3 years, their amazing support is another reason why we wouldn't consider anyone else at this point.
We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as compared to the other major players in Azure and AWS.
Google Compute Engine provides a one stop solution for all the complex features and the UI is better than Amazon's EC2 and Azure Machine Learning for ease of usability. It's always good to have an eco-system of products from Google as it's one of the most used search engine and IoT services provider, which helps with ease of integration and updates in the future.
Although I use only a fraction of their product offerings, the total set makes scalability an easy goal to shoot for. As I said, I have a few customers that use the services my Linode provides...and I like it that way. However, should I need to scale up, I can...without incurring any more cost than I need to.
Effective integration to other java based frameworks.
Time to market is very quick. Build, test, deploy and use.
The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.