Amazon Elastic Container Service (Amazon ECS) is a scalable, high performance container management service that supports Docker containers.
$0
per hour per GB
Akamai Cloud Computing
Score 9.0 out of 10
N/A
Akamai Cloud Computing (formerly Linode) accelerates innovation with scalable and accessible Linux cloud solutions and services. These products, services, and people give developers and enterprises the flexibility and support to build, deploy, secure, and scale applications more easily from cloud to edge on Akamai's distributed network.
There is no additional charge for Amazon ECS. You pay for AWS resources (e.g., Amazon EC2 instances or Amazon EBS volumes) you create to store and run your application. You only pay for what you use, as you use it; there are no minimum fees and no upfront commitments.
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.
As a VPS provider, equally as functional for my needs as Amazon, Linode is less flexible (con), but also easier to use (pro). DigitalOcean seems equally good on many aspects, maybe they are ahead on adopting new/useful technologies. I wish Linode supported Fargate like container …
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.
Linode provides a wide range of configurations and prices, suitable for many budgets and needs. They also have a lot of experience in providing these services for many years. We have almost exclusively used Debian distributions for our work, but they offer a large number of other versions of Linux. Beside "raw" distributions of Linux, they also offer other VMs containing specialized installations of a variety of applications, such as Wordpress, Drupal and Docker.
One of the biggest advantages is the flexibility to change underlying EC2 instances. As the traffic or demand increases, we can easily change EC2 instances without any issues.
Amazon ECS APIs are extremely robust and one can start and stop containers by firing one post request only. So, it is not mandatory to keep the demo solutions up for every time. Just at the time of demo fire the command - make the container up and running - do the demo - down the container with API. A simple portal can control every container which helps non-technical (sales, marketing) to do the demo without keeping the solutions up for the entire time frame.
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.
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.
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.
Linode is an infrastructure provider issues related to performance are really on me. Linode provides a capable infrastructure and allows me to tailor performance of the services I provide to my customers to my specific situation. Linode allows me to implement "tweaks" that, from experience, I know will do the job with little risk without a whole bunch of static from idiot support 'droids who just get in the way ("this isn't supported at the present time").
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.
Support from Linode has always been excellent for us. We've barely had to wait any time between ticket requests and replies, and we've always received replies that actually answered our problems. Whenever maintenance has occurred on Linode's side, they've always alerted us beforehand and left a ticket open as a source of communication in case we had any issues after maintenance or any other questions that we needed answered.
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.
EKS is a Kubernetes technology and you need to learn Kubernetes and build a cluster before using it. So there's a learning curve here. ECS was easier to implement and simpler to have in our use case. It takes less time to run a workload and make it available.
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 are overkill. Compared specifically to some of its closest rivals: Versus DigitalOcean, Linode has better pricing for VMs; while compared to Vultr, while Vultr's backups are cheaper (20% of VM cost versus effective ~25% of VM cost), Vultr's DDoS protection is an add-on product, which made the overall cost of the deployment more expensive. The runner-up competitor for our use cases, Hetzner, offers superior pricing; However due to their flaky KYC and anti-fraud which was a pain to deal with, I lost faith in them. They also do not have a region in East Asia, which would impact performance.
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.
The autoscaling kept the performance of the services great.
We saved money by running the workloads on AWS ECS in Fargate mode by having different settings for different services to save on the hardware configuration side as well as having scheduled tasks.
