Akamai Connected Cloud (Linode) vs Google Kubernetes Engine comparison

"When it comes to the Linode Kubernetes Engine and the amount of automation it provides, it's awesome, it's a game-changer. If a process randomly dies, it could take me a while to notice that it has died, if I haven't set up monitoring. With Kubernetes, it will just restart itself using Heartbeats."

"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."

"The number one thing we like about Linode isn't necessarily a service, it's their support. We've found their support to be absolutely fantastic. They've been so outstanding with their support. Every single time we call them and we ask for advice or help, they go above and beyond and it's really made us appreciate what they do."

"The most valuable feature is that they are flexible and easy to get ahold of if I need something."

"Generally speaking, I have not found any faults using Linode. For what we wanted, they provided a complete solution."

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

"The virtual machine configuration tool is very helpful for setting up a new server or for modifying an existing server."

"The fact that you can do any Linux distribution is great. You can try out any Linux distribution, even some of the more obscure ones, and they are always keeping them up-to-date. As soon as a new distribution comes out, it is on the platform pretty much the same day, which I find really helpful."

"It is easy to use and deploy."

"GKE's plugin management and configuration sync are excellent features. The amount of data it provides is good, and I've been able to integrate it with the things I need."

"The main advantage of GKE is that it is a managed service. This means that Google is responsible for managing the master node in the Kubernetes cluster system. As a result, we can focus on deploying applications to the slaves, while Google handles any updates and security patches. The fact that GKE is fully integrated into the Google ecosystem, including solutions such as BigQuery and VertexAI. This makes it easier for us to integrate these tools into our process. This integration ultimately speeds up our time to market and reduces the time and effort spent on managing infrastructure. The managed aspect of GKE allows us to simply deploy and utilize it without having to worry about the technicalities of infrastructure management."

"Google Kubernetes Engine's most valuable feature is container deployment."

"The scalability is the best feature."

"Google Kubernetes Engine's most valuable features are microservices and its acquisition rate, which is very useful for scaling perspective."

"The features are typical Kubernetes, but Google One offers a better GUI-based deployment. It's more sophisticated and integrates well with other services, providing a better customer experience."

"Stability-wise, this solution is really good."

"One thing that I'd really like to see is auto-scaling node pools for their Kubernetes. I don't think that they have that. That's a huge one and would be very helpful. Specifically, what I would like is auto-scaling node pools that would scale down to zero nodes, which is tricky. That's very important for certain use cases."

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

"The product must improve its security."

"I would like Linode (without cluttering things) to provide some type of DevOps workflow where people are configuring their pipelines from running their tests and deploying to their test server. Once approved by clicking a button, it just gets deployed to production. I would like something like Azure DevOps, which we use for large applications, and would be something nice to have in Linode."

"The network between different servers isn't very good. I have to install additional solutions to link the servers with each other."

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

"Before they changed the dashboard, I found some of the more granular options easier to find."

"It's not really an issue with Linode itself but upgrading Linux major versions can be challenging. It would be be fantastic if Linode developed a way to ease transitioning to a major new Linux upgrade."

"An area in which Google Kubernetes Engine could improve is configuration."

"While the GKE cluster is secure, application-level security is an essential aspect that needs to be addressed. The security provided by GKE includes the security of communication between nodes within the cluster and the basic features of Kubernetes security. However, these features may not be sufficient for the security needs of an enterprise. Additional security measures must be added to ensure adequate protection. It has become a common practice to deploy security tools within a Kubernetes cluster. It would be ideal if these tools were included as part of the package, as this is a standard requirement in the industry. Thus, application-level security should be integrated into GKE for improved security measures."

"I would like to see the ability to create multiple notebook configurations."

"The product's integration with third-party vendors needs improvement."

"I would rate the scalability a seven out of ten."

"The management UI could be improved. When looking at the web interface, it feels kind of slow due to the many features involved."

"The user interface is a bit confusing sometimes. You need to navigate between the various consoles we have. It's hard to figure out where things are. It's frustrating. The documentation could be a bit better."

"The monitoring part requires some serious improvements in Google Kubernetes Engine, as it does not have very good monitoring consoles."

"One key difference is that pricing is very hard to come by and to understand with all the bigger companies. Their pricing models are so weird and it's hard to figure out exactly how much I am going to pay for this kind of service. Everything is piecemeal. With Linode, it's simple and straightforward. You know exactly what you will have to pay at the end of the day."

"The solution is neither cheap nor expensive."

"I pay $5 per month for each of three servers, for a total of $15 per month, and I normally prepay a few months in advance."

"Being that they are small, their prices are slightly higher than the large providers like Amazon if you compare raw computing power."

"is a little cheaper than Google or Amazon, more or less on par with the other competitors."

"It is quite affordable, which makes it a great choice."

"The pricing model is simple."

"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."

"The price for Google Kubernetes Engine could be lower - I'd rate its pricing at three out of five."

"I rate the product's price a six on a scale of one to ten, where one is low price and ten is high price. The product is competitively priced."

"The tool's licensing costs are yearly."

"Its pricing is good. They bill us only per user. That's nice."

"I would rate the solution's pricing a nine out of ten. The tool costs around 3000 dollars per month. There are no additional costs apart from these."

"Initially, Google Kubernetes Engine was a little bit cheaper, but now its prices have been increased compared to the pricing model and the features that are made available by its competitors."

"I would rate Kubernetes' pricing four out of five."

"This is an open source solution, so there is no pricing or licensing."