Akamai Cloud Computing vs. Amazon Elastic Container Service (Amazon ECS)

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

Amazon Elastic Container Service (Amazon ECS) is well suited where you need the ease of managing the clusters by letting AWS do the stuff for you. Obviously, whenever you want to run the docker based workloads, it is always better to go for either AWS ECS or AWS EKS. If you are interested in staying at AWS only and don't want to be cloud-agnostic, then go for AWS ECS instead of AWS EKS. AWS ECS is cheaper than AWS EKS and also more managed by AWS and better integrated with other AWS services. If you want to run those workloads as serverless, then AWS ECS Fargate is the best option to go with. If you already have a Kubernetes based setup that you want to migrate to AWS, then go for AWS EKS instead of AWS ECS.

Incentivized

• Many locations of datacenter
• Wide selection of pre-installed applications in the marketplace
• Price is very affordable.
• User interface in the account panel is easy to understand.
• Fast server
• Linode provides tutorials for new users thru Youtube channel.
• Payment is per usage, not monthly.
• Responsive customer service

Incentivized

• Well Integrated - As with the majority of AWS services, ECS works will with any other AWS product (Route 53, CloudWatch, IAM, etc).
• Easy to get started with - It is easy to get started building just about anything in AWS and using ECS is no exception to this rule. Be careful though -- AWS lets you do/build anything in any way you could think of and allowing yourself to shoot yourself in the foot is no exception.

Incentivized

• 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

• The user interface sometimes seem to be confusing and cumbersome. It can be improved so that people can understand clearly which section to go for which functionality.
• When a container fails, the error logs are not readily available on the ECS console. If it can be provided it would be easier to debug from there itself instead of going to our log manager.
• Sometimes the old EC2 containers become stale and need to be restarted manually. There should be a notification for such scenarios. We have mostly been finding it out on our own and then fixing it by manually restarting EC2 instances.
• If this could be proactively monitored and notified, it would be great.

Incentivized

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.

Incentivized

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.

Incentivized

Aside from some ECS-specific terms to learn at first, learning & starting to use ECS is relatively straightforward. AWS docs on the topic are also of high quality, with sound & relevant examples to follow. Troubleshooting container issues is also a breeze thanks to CloudWatch integration & helpful error messages on the AWS console.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

Support is relatively good, although the documentation sometimes is lacking, as well as outdated in our experience, especially when we initiated the process of using this service. But once we found how to assemble things, we haven't really required support from anyone at AWS, the service works without problems so we haven't had the need to contact support, which speaks well of how ECS is built.

Incentivized

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

Incentivized

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.

Incentivized

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.

Incentivized

AWS Elastic Beanstalk is a good beginner level orchestration service but lacks container management and scaling capabilities. EC2 is again not a Managed cloud service. It is like just renting a computer on cloud and then managing it on our own. Compared to these ECS is a comprehensive solution that provides management, scaling, containerization and other service connectivity out of the box.

Incentivized

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.

Incentivized

• Over the years, Linode has enabled us to stop maintaining our own server hardware, and leave that up to them.
• On the other hand, Linode provides a bare machine, and requires us to provide almost all of the systems administration effort.

Incentivized

• We run 8 web applications (demo instances) on a single machine. At a particular time, no more than 3 applications run simultaneously. So, we keep only required containers up. This helps us to provision small EC2 machines without compromising performance.
• Overall Amazon ECS helps to have less number of dedicated machines as more than one solution can be deployed on a single instance. This reduces costs a lot.

Incentivized