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.
N/A
Amazon Web Services
Score 8.6 out of 10
N/A
Amazon Web Services (AWS) is a subsidiary of Amazon that provides on-demand cloud computing services. With over 165 services offered, AWS services can provide users with a comprehensive suite of infrastructure and computing building blocks and tools.
$0
per month
Pricing
Akamai Cloud Computing
Amazon Web Services
Editions & Modules
No answers on this topic
Free Tier
$0
per month
Basic Environment
$100 - $200
per month
Intermediate Environment
$250 - $600
per month
Advanced Environment
$600-$2500
per month
Offerings
Pricing Offerings
Akamai Cloud Computing
Amazon Web Services
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
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.
AWS allows a “save when you commit” option that offers lower prices when you sign up for a 1- or 3- year term that includes an AWS service or category of services.
Better efficiency, better cost savings, improved Return on Investments. Overall the Akamai Connected Cloud (Linode) cloud solutions are a step above the competition in regards to all categories. We prefer it for several reasons but the one that stands out is the cost and …
It is more user-friendly than the big three cloud providers like AWS and GCP. The interface blows them out of the water; pricing is so much more competitive—no egregious bandwidth fees like AWS. As a small startup, cutting out the overhead of ultra-complex UI and pricing …
The thing that caught my eye was the price to start with. I move to Digital Ocean because they had better options for virtual network isolation, but I came back as soon as Linode fixed the issue. There support is great and things just work.
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 …
I could not talk to anyone at all with digital ocean. I still cant turn off their billing. I hate those guys. They are good for techies - terrible for small co. owner like me that does not have techie staff on hand every day
We evaluated DigitalOcean vs. Elastic Beanstalk before Linode, which was pretty cost intensive for deploying basic machines in the cloud for experimentation purposes. So, we had to switch to Linode for cost-effectiveness and default security mechanisms built inside Linode.
Compared to the big cloud players like Amazon Web Services, Google Cloud Platform, MS Azure, Oracle Cloud, and co., Linode's product is simpler and cheaper. For quick and straightforward client engagements, the power and flexibility afforded by the previously mentioned vendors …
We've used larger solutions, including AWS, Azure, Google Cloud, and Oracle Cloud. In each case, the pricing was confusing and, with all of the add-ons needed for even a simple infrastructure, ended up being several times the cost of a similar Linode solution. On the flip side, …
Linode's offering is almost identical to DigitalOcean's, but I find Linode's customer service better AWS, Azure and Google Cloud provide all services Linode does, but provides a much large set of other features and customizations.
I personally feel that Linode platform is more stable and faster than other platforms. While other are great Linode has never let me down. I've hosted with other providers for clients because that's who they were using and they definitely go down more than Linode has.
Linode delivers higher performance cloud servers, within an easier web interface, simpler API, and better cost-benefit. Amazon has a complex interface that many times make the customers spend much more time in order to finish simple tasks and use "AWS-terms" so even if you need …
Linode has a much better range of data center locations than DigitalOcean. DigitalOcean has slightly better pricing and included backups( not extra backup fees like with Linode)
Linode offers the most applicable services to the users through Cloud deployment and easy data management capabilities, and even easy project cost management. The features adaptation is easy and quality services from the migration of data and demand monitoring and the project …
I've had performance issues with other providers, and when running workloads where CPU performance is vitally important, my experience with Linode has been excellent. The cloud landscape is crowded, and I think it's important to know why one vendor might stand out amongst …
I chose Linode instead of AWS and Google Compute for two reasons: 1. Cost: With Linode, I can deploy a Linux VPS as cheap as 5 a month that meets my website requirements. 2. User Interface: I admit that AWS EC2 and Google Compute are too complicated for me, but Linode is easy …
In my personal experience, AWS is superior to both GCP and Azure in the majority of usable applications. GCP suffers from the near total misunderstanding of how support system is even supposed to work, and while _some_ services are pretty nifty and well-polished, some are …
AWS stands out in its ability to adapt technology more quickly. All the new features, first adapted by AWS, make it the market leader. The key metrics, such as MTTR, are among the best among all other cloud service providers. The AWS dashboard and analytics features are very …
Amazon Web Services Lambda supports more triggers, richer language/runtime support, and has tighter integrations with Amazon Web Services, as compared to Azure/Google Cloud functions.Amazon Web Services also has better global infrastructure, with 33 regions and 105 availability …
We tried various other cloud providers and features provided by them. Many of the cloud providers have similar features but there are few factors which make Amazon Web Services cloud as preferable choice of our bank are cost, location of Amazon Web Services datacenter where it …
Apart from Amazon Web Services, we use Microsoft Azure in some of our projects. I have some basic experience in Google Cloud Platform (GCP) as well. If given a choice, I would prefer using Amazon Web Services over Azure or GCP. I find provisioning of resources relatively faster …
Amazon Web Services is better among all of them due to its performance, stability, security and navigation. It effectively saves the cost and provides better facilities than the other competitors. It plays great role when it comes to user friendly interface. It also provided …
AWS has the largest market share and most established and over 200 services for diverse needs. AWS has a very power user interface and pay as you go work well that others. AWS has the by far largest network of data centers for low latency and high availability. The regular …
Better global availability and use across industries. AWS has a great ecosystem of experts, developers, solution architects and it helps to get to know them at various AWS events across the world
Amazon Web Services is much more mature than all of the cloud service providers out in the market. It has 300+ services that solve almost all of your cloud problems.
Compared to other providers like Google Cloud Platform(GCP) and Microsoft Azure, [Amazon Web Services] has a wider range of services, which help you easier implement the solution you want. Also, they have been in the market for more years than their competitors. Moreover, they …
Amazon SageMaker is being extensively used by our R&D department for machine learning models development and research purposes. We work in Jupyter notebooks hosted on SageMaker notebook instances rather than notebooks hosted in local machines by doing so most ML algorithms …
I feel AWS usage of services by global clients has been the most compared to Azure or Openshift. AWS service offering's and usage are economical and much more secured. Its has build an ecosystem of providing all the services capabilities under one umbrella . It provides …
The decision was made to go with AWS because of name recognition and familiarity by contractors we hired. I checked out Google Compute Engine a few years ago, and it did have similar option set, however Google in general was behind Amazon's offerings.
Amazon Web Services fits best for all levels of organisations like startup, mid level or enterprise. The services are easy to use and doesn't require a high level of understanding as you can learn via blogs or youtube videos. AWS is Reasonable in cost as the plan is pay as you …
Amazon Web Services is well suited when we have a huge amount of data to store, process, manipulate and get meaningful information out of. It is also suitable when we need very fast data retrieval from the database. They provide a superior product at a fair price which allows …
Both the services are in the field for quite sometime. And the biggest competitor of Amazon Web Services is Microsoft Azure. Though, Azure easily connects with Microsoft services like a jelly, even in AWS its so easy. And the best thing is due to its vast variety community …
Amazon Web Services has a much more seasoned and known set of tools. The learning resources and documentation is much more prevalent and applicable to more scenarios which definitely helps with implementation. Google cloud does offer comparable products, and the user interface …
We evaluated Google Cloud and Azure at the beginning of our cloud journey but at that time, AWS was so far ahead of the other public cloud providers that there was no question about whether or not to go with AWS. They have the broadest catalog of services and their support is …
We have investigated Azure as well, for this specific need it made the most sense to go with [Amazon Web Services], the design was much simpler to get going. We have also used Azure for some of the other deployments that we have done with SaaS systems. These are the two …
Our tech team was comfortable with Amazon Web Services and that is why we started with Amazon Web Services. In the meantime, we searched for other services like Amazon Web Services but it seems that facilities like Elastic Bean and the first year free made us stick to Amazon …
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
We are using RDS for the database services. With RDS, we don't have to manage much, as most of the DBA tasks are automated. For development purposes, we are using Kubernetes pods, which makes it easy to deploy applications and scale up as needed. AWS integration with in-house applications is seamless, making it easy to keep a data-sensitive application on-premises while still utilizing AWS services.
The (new) 'create custom image' function needs a bit of work before it is useable.
New accounts have limited features until a support requested is made to turn specific ones on. It would be useful to have an account page that tells you what is disabled so unpleasant surprises are not had at the pointy end of a deadline.
Stackscripts would be better if it more info was transferred to the script. Eg the Linode Label given, plan requested, etc. But now I am just nit-picking
In this eight years of being Linode's customer, there hasn't been a single day we faced problem. Even the migration or maintenance activities have been planned, organised and priorly informed. Kudos to taking care of even such small metrics. Though the instances are unmanaged, the support team helps with relevant document links, or their own articles that help us to fix or solve the issues we face.
I would gladly rely on AWS for any large-scale application deployment. For prototyping and small-scale applications, a more heavily managed environment on top of the 'bare metal' virtual infrastructure, such as Heroku or Elastic Bean Stalk, is probably a more productive approach in most cases
It's pretty easy for me, but I preferred their old interface before it was called 'cloud' (not a computer science term.) The new interface looks easier but I had to ask for help for things I used to be able to find myself. If someone was new to it--without having used their old interface--it might be easier for them than it originally was for me.
Amazon Web Services is a great tool when it comes to middle size organizations like us. It provides multiple tools and functionalities in low costs. The best feature we have to pay as we go. No financial burden on company for the unused instances. It also comes with greater level of security such as two level authorization such as multi factor authorization.
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.
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.
AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.
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.
The customer support of Amazon Web Services are quick in their responses. I appreciate its entire team, which works amazingly, and provides professional support. AWS is a great tool, indeed, to provide customers a suitable way to immediately search for their compatible software's and also to guide them in a good direction. Moreover, this product is a good suggestion for every type of company because of its affordability and ease of use.
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.
It is more user-friendly than the big three cloud providers like AWS and GCP. The interface blows them out of the water; pricing is so much more competitive—no egregious bandwidth fees like AWS. As a small startup, cutting out the overhead of ultra-complex UI and pricing dramatically helps. It seems to be matched tit-for-tat with DigitalOcean, and their UI is similar in many ways. DigitalOcean has more mature capabilities, even though Linode/Akamai was founded earlier. Linode/Akamai provides better price-per-performance, though, as DigitalOcean is expensive nowadays.
In my personal experience, AWS is superior to both GCP and Azure in the majority of usable applications. GCP suffers from the near total misunderstanding of how support system is even supposed to work, and while _some_ services are pretty nifty and well-polished, some are mindbogglingly designed black boxes with self-conflicting documentation. Some of it comes from having legacy systems, sure, but AWS somehow manages, even having a rather big lead start. Azure, from my limited experience, is limited to people somehow coerced into its usage by external constraints. That being said, IF you can design and implement something there, it will probably run fine.
I completely agree with the above statement. Linode provides the best option in terms of configurations and scalability. We have chosen share CPU instances many times and then moved on with dedicated CPU instances, just with a click of button.
Provisioning resources like large database instances is really quick. We can easily scale our instances up or down as per need.
Storing files in S3 instead of onprem NAS drives is much more economical, especially for the files stored in glacier deep archive for compliance purposes.
Backup snapshots of EBS volumes and RDS instances may increase the cost of cloud if not cleaned up properly.