Akamai Connected Cloud (Linode) vs Kubernetes comparison

"For my usage, which is a small business, I rate the scalability of Akamai Connected Cloud (Linode) around nine or ten."

"Because of the way that their pricing model is set up, I can scale up or down the size of a customer's server very easily. It makes life very easy for me when they run out of space, need more speed or RAM, etc. I can very easily pay the difference and reboot the machine, and now I have the upgrade that I wanted. That just makes it extremely simple."

"Linode offers cost-effective pricing, and it enables me to swiftly deploy my services."

"The ability to fire up a virtual machine, use it, and then kill it, is quite a valuable feature for me."

"It has helped to minimize the risk and scale services at large in virtually no time."

"It is also important that Linode offers worldwide coverage via multiple data centers. The ability to deploy on multiple servers, worldwide, allows us to have distributed services and failover and redundancy."

"The cloud management panel is nice."

"Service availability is the most valuable feature. It gives every user 100 percent uptime."

"We find the smooth, instant fail-safes in this solution to be very useful, as this allows for easy revival of dying quads or failing applications."

"The most valuable feature of Kubernetes is automation. It is the best tool for automation."

"We use this solution for the hosting of micro-services. Kubernetes helps us to orchestrate all the containers hosting these micro-services."

"The most valuable feature of Kubernetes is container orchestration."

"The autoscaling feature is the most valuable. Kubernetes itself is an orchestration tool. It automatically detects the load, and it automatically spins up the new Pod in the form of a new microservice deployment."

"Kubernetes' most valuable features are scaling, deployment, and container management."

"It has a complete loading feature set for replica site deployment."

"One of the most valuable features is the thickness of the cloud platform or on-prem file, which makes the solution straightforward to shift and scale. It works well with different types of deployment strategies and networks."

"They don't have role-based access control, which is problematic for us."

"Our primary concern is always the latency."

"Its cost can be improved."

"The Cloud Manager interface sometimes feels slow, particularly when accessed from Asia."

"The suitability of this solution depends on the features that you need. If you're an Uber-sized company then you're probably not going to want to start using Linode. If you are a large-sized organization then you're going to want to start using one of the bigger providers that gives you the scalability and the feature set that you are probably going to be needing in the future."

"I've had some difficulties with some of their IP addresses being banned by certain mail servers."

"I would like to see more seamless integration with backup, although it's pretty easy to do."

"It would be nice if they had more data centers in Latin America."

"The tool needs to improve its UI. The tool is very complex and basic."

"Kubernetes can improve by providing a service offering catalog that can be readily populated in Kubernetes."

"The management needs to be improved."

"Honestly, there is not much I like about Kubernetes. It's very complicated to deal with. I just do it because I have to."

"Kubernetes is a bit complex, and there's a steep learning curve. At the same time, I cannot imagine how it could be easier. You need many add-ons to it, and the commercial releases of Kubernetes should address that."

"The Kubernetes dashboard can be improved. It is currently a mess. We were using Rancher earlier, and everyone was happy with the dashboard. Right now, we are using Kubernetes, and it's not working with Microsoft workstations. We still have problems with the dashboard. It's terrible."

"The plugins could be better. That is one pain point we had, and we had to get in with many other open standards, like Calico networking and more."

"Kubernetes could improve security. The security is really hard to deploy with proxies and other elements. Additionally, We have had some issues downloading repos and libraries."

"The pricing model is very simple. I like the simplicity of it, starting at $5, then doubling as it goes up from there. That is a brilliant idea, and it is not complex at all. It is about as dead simple as you can imagine. So, if you want to double what you have, then you double your price, pay the money, and reboot. It is done. It's that simple. You can't beat that."

"Currently, we are at $40 a month but they have costly solutions as well."

"Pricing-wise, I find it simple in that they give you a monthly fee, but they also charge it hourly. So, if you are using the service for a small part of the month, then you are only paying for that small amount instead of a whole month, like with other providers. It is a flat monthly fee if you use the service for the entire month. It just makes things so simple. Because they are focusing on Linux, you don't have to worry about licensing costs of Windows and things like that. So, the price that they give you is the price that you need to pay each month. I just find it so simple compared to the likes of AWS and Azure. It is nice, easy, and predictable. I know exactly what I am going to be paying each month and what resources I get for that price."

"The monthly cost depends on your requirements."

"Compared to other providers, I find Linode's pricing a bit higher. Storage could be more affordable."

"Overall, it is cost-effective. They offer flat, no lock-in pricing. We also get discounts. As compared to its competitors, it is costly, but at the same time, it has many features."

"The pricing model is very simple. If you have very small applications, you can use the plan which costs $5 per month. That gives you 50 GB of memory and almost 1 GB of RAM. If you need more than you have to select the next plan which is $10 per month, which has about 70 GB of data and 2 GB of RAM."

"The value for the price is really good."

"The solution is open source and has no fees."

"Kubernetes is open source. But we have to manage Kubernetes as a team, and the overhead is a bit high. Compared with the platforms like Cloud Foundry, which has a much less operational overhead. Kubernetes, I have to manage the code, and I have to hire the developers. If someone has a product, a developer should know exactly what he's writing or high availability, and all those things may differ the costs."

"The solution itself is open-source, so there is no cost attached to it. However, it requires a virtual machine to operate, which does come at a cost; a choice of a pay as you go model, or a monthly charge via an enterprise agreement. There is a pricing calculator available, where organizations can determine the level and number of virtual machines required, and how much that will cost."

"In addition to Kubernetes, you have to pay for support."

"The management layer is free, which is perfect. You don't need to pay money for the management layer, but in AWS develop service, you need to pay. I think it is €75 per month for the management layer. It is free here, so you can have as many Kubernetes clusters as you need. You are paying just for the workload, that is, for the machine, CPU, memory, and everything."

"I am using the solution's open-source version."

"The price of Kubernetes could be lower. However, it is less expensive than VMware Tanzu. Additionally, technical support is expensive. The overall cost of the solution is approximately $1,000 annually."

"Kubernetes is open-source."