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
Amazon RDS
Score 8.4 out of 10
N/A
Amazon Relational Database Service (Amazon RDS) is a database-as-a-service (DBaaS) from Amazon Web Services.
N/A
Google Compute Engine
Score 8.6 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
Amazon Relational Database Service (RDS)
Google Compute Engine
Editions & Modules
No answers on this topic
Amazon RDS for PostgreSQL
$0.24 ($0.48)
per hour, R5 Large (R5 Extra Large)
Amazon RDS for MariaDB
$0.25 ($0.50)
per hour, R5 Large (R5 Extra Large)
Amazon RDS for MySQL
$0.29 ($0.58)
per hour, R5 Large (R5 Extra Large)
Amazon RDS for Oracle
$0.482 ($0.964)
per hour, R5 Large (R5 Extra Large)
Amazon RDS for SQL Server
$1.02 ($1.52)
per hour, R5 Large (R5 Extra Large)
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
Amazon RDS
Google Compute Engine
Free Trial
Yes
No
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
Optional
Optional
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.
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.
I used a lot of different services, a lot of services inside Amazon AWS and Digital ocean, but I found at Linode a different way to do all what I need, without having to be worried about weird costs calculations and other things like that.
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 …
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) …
The billing process is way easier with Linode. Linode's servers feel way faster and have good connectivity with places we really need. Stack scripts to help building up servers are another great feature alongside their forum and Q&A.
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 …
Verified User
Director
Chose Google Compute Engine
The two products are very similar. For what we use each for, the difference is negligible, and we actually use both AWS EC2 and Google Compute Engine GCE.
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
If your application needs a relational data store and uses other AWS services, AWS RDS is a no-brainer. It offers all the traditional database features, makes it a snap to set up, creates cross-region replication, has advanced security, built-in monitoring, and much more at a very good price. You can also set up streaming to a data lake using various other AWS services on your RDS.
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.
Automated Database Management: We use it for streamlining routine tasks like software patching and database backups.
Scalability on Demand: we use it to handle traffic spikes, scaling both vertically and horizontally.
Database Engine Compatibility: It works amazingly with multiple database engines used by different departments within our organization including MySQL, PostgreSQL, SQL Server, and Oracle.
Monitoring: It covers our extensive monitoring and logging, and also has great compatibility with Amazon CloudWatch
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
It is a little difficult to configure and connect to an RDS instance. The integration with ECS can be made more seamless.
Exploring features within RDS is not very easy and intuitive. Either a human friendly documentation should be added or the User Interface be made intuitive so that people can explore and find features on their own.
There should be tools to analyze cost and minimize it according to the usage.
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.
We do renew our use of Amazon Relational Database Service. We don't have any problems faced with RDS in place. RDS has taken away lot of overhead of hosting database, managing the database and keeping a team just to manage database. Even the backup, security and recovery another overhead that has been taken away by RDS. So, we will keep on using RDS.
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've been using AWS Relational Database Services in several projects in different environments and from the AWS products, maybe this one together to EC2 are my favourite. They deliver what they promise. Reliable, fast, easy and with a fair price (in comparison to commercial products which have obscure license agreements).
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.
I have only had good experiences in working with AWS support. I will admit that my experience comes from the benefit of having a premium tier of support but even working with free-tier accounts I have not had problems getting help with AWS products when needed. And most often, the docs do a pretty good job of explaining how to operate a service so a quick spin through the docs has been useful in solving problems.
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.
Amazon Relational Database Service (RDS) stands out among similar products due to its seamless integration with other AWS services, automated backups, and multi-AZ deployments for high availability. Its support for various database engines, such as MySQL, PostgreSQL, and Oracle, provides flexibility. Additionally, RDS offers managed security features, including encryption and IAM integration, enhancing data protection. The pay-as-you-go pricing model makes it cost-effective. Overall, Amazon RDS excels in ease of use, scalability, and a comprehensive feature set, making it a top choice for organizations seeking a reliable and scalable managed relational database service in the cloud.
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.