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
Mirantis Kubernetes Engine
Score 9.4 out of 10
N/A
The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters on any infrastructure: public cloud, private cloud, or bare metal.
$0
per year
Pricing
Akamai Cloud Computing
Mirantis Kubernetes Engine
Editions & Modules
No answers on this topic
Free
$0.00
per year
Basic
$500.00
per year
Offerings
Pricing Offerings
Akamai Cloud Computing
Mirantis Kubernetes Engine
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.
These pricing options are compatible with Linux or Windows Server and are per year, per node. The basic version requires maximum online purchase not to exceed 50 nodes. Support/professional services are not included.
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
Docker is great for when you would want to use a VM for any given application, but don't need the overhead of the whole OS. Docker containers use very little computing resources, boot up very quickly, and are very easy to set up. An instance where Docker may not be appropriate would be for an application that requires good security. If in this situation, a true VM would probably be your best bet.
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
Docker has a bit of a learning curve, and it takes some time to become familiar with the tooling and syntax. Transitioning an existing architecture to docker can represent a significant investment.
Docker attempts to provide some level of cross-host container orchestration via swarm, but it falls short of third-party solutions like kubernetes.
We occasionally run into stability issues when the docker daemon is subjected to high load (many applications starting/stopping frequently). In these cases, docker hangs and we have to restart or replace the node.
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.
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.
Docker's CLI has a lot of options, and they aren't all intuitive. And there are so many tools in the space (Docker Compose, Docker Swarm, etc) that have their own configuration as well. So while there is a lot to learn, most concepts transfer easily and can be learned once and applied across everything.
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.
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 community support for Docker is fantastic. There is almost always an answer for any issue I might encounter day-to-day, either on Stack Overflow, a helpful blog post, or the community Slack workspace. I've never come across a problem that I was unable to solve via some searching around in the community.
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.
I have not used any other software as a container management solution. Its containerized apps allow the usage of less memory, thus they start and shut down very fast. This tool is helping the enterprise software to work quickly against the changing conditions thus offers great scaling by simultaneously allowing me to meet the demands, which also leads to easy implementation of the strategies.
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.
We are able to try things very quickly compared to before. If you need to debug it, changes on X/Y/Z will have an impact on the way your app works, and changing libraries or configurations of the environment easily can improve your development cycles.
In case someone new arrives, the onboarding is pretty easy thanks to Docker. We have tried many configs and images until we reached a point were we have what we want. We don't have to painfully do that again for every new user. We just send him the image.
