Cheap, Fast, Stable. Pick 2. No, pick 3!
Overall Satisfaction with Linode
Linode runs for many years all of the infrastructure we need for our web pages and all our public Internet-facing applications. While over the year we used other providers in additions, none were better. It's nice to be able to provision VMs all over the globe, just like we can do with the usual cloud providers, and yet due to their scale, we still feel we get much better and much more personal support when needed.
Pros
- Pricing and pricing structure.
- API access and API documentation.
- Simple yet effective UI.
- Kubernetes offering.
Cons
- I'd love to see managed DB capabilities offered.
- NodeBalancers are surprisingly expensive compared to VMs.
- VPC like GCP does (crossing sites).
- Stability for our Internet-facing services.
- Cost savings.
- Flexibility to provision a handful of servers temporarily.
- Amazon Elastic Compute Cloud (EC2), Oracle Cloud Infrastructure Compute, Google Compute Engine and DigitalOcean Droplets
For simple VMs or Kubernetes, Linode is cheaper and it also has consistently good performance. As long as this is what you need, you get all you'd want.
AWS and GCP shine when you need their other services. Oracle Cloud was bare bone and expensive. Droplets are easy to start with, but get expensive fast.
AWS and GCP shine when you need their other services. Oracle Cloud was bare bone and expensive. Droplets are easy to start with, but get expensive fast.
The predictable costs of Linode infrastructure (VMs, storage, network) makes it very simple to do budgeting for our infrastructure. Other cloud providers seem to prefer to have VMs provisioned for minutes and hours and then they are very cheap, but for 24x7 and varying workloads, the costs get less predictable and usually they are significantly higher.
It's easy to get another set of servers on Linode as I know it'll not increase much.
It's easy to get another set of servers on Linode as I know it'll not increase much.
Infrastructure uptime means we can serve our customers 24x7 as it should be. This is nowadays not a big problem of course as setting up a HA environment is standard nowadays (some servers, some load balancers, some DNS entries, replicated DBs), but having rock solid infrastructure you can mostly depend on, just simplifies your life and reduces outages or near-outages.
The stability we saw in the last 9 years also means we don't have to use another cloud provider as a Plan B.
The stability we saw in the last 9 years also means we don't have to use another cloud provider as a Plan B.
Using Linode
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Quick to learn Convenient Feel confident using | Lots to learn |
- DNS management via UI.
- Kubernetes with its hosted management plane.
- Costing structure.
- Layer 2 VLAN.
- Regions for Object storage very limited.
Comments
Please log in to join the conversation