Competitive pricing and good service quality
March 18, 2021

Competitive pricing and good service quality

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Linode

It's being used by the department of mine. We use Linode as the the infrastructure (IaaS) of IT systems which our department is using internally. As the main work of my department is software development related, we set up a few internal systems to manage software source code (git), automatically test code, track issues, manage employees KPI, and others.
  • Competitive price.
  • Service stability is pretty good.
  • Easy to use comparing to rivals
  • Provide special offers during Black Friday, etc
  • Provide more types of service, such as k8s cluster
  • Lower pricing of some types of service
  • We [don't spend] much on Linode.
Google Computer Engine: it is too expensive. You have to pay for computing resources (CPU, memory), storage, network traffic individually. While the quality of service is good, it's still with the same level of Linode.

Amazon Web Services: it's more affordable, comparable to Linode. However, it's pretty hard to use. The Amazon web service dashboard is pretty bad, poor designed UI, poor organized documents.
In most cases we do not need Linode support. We encountered some problems in deed, which are mostly hardware problems after Linode upgraded their servers. After we contacted Linode support, they resolved the problems quickly.
Direct cost: a few servers starting from 5$/m to 20$/m, totally hundred of dollars per month.

Indirect cost: one fully paid administrator to manage the servers and IT systems on it.
We use Linode as the infrastructure of our internal IT systems. So the uptime is not so much critical. One or two hours downtime is acceptable. We set up a script to periodly back up the data on Linode servers to AWS s3 in case of fatal accident. In past a few years, however, we never used the backup data.
Where Linode is well suited:
  • As hosting of general IT systems which run on one or few nodes.
  • For test, quick prototype verification, quick deployment, etc.

Where it is less appropriate:

  • As critical persistent data storage. I prefer to use Amazon S3 instead for such scenario.
  • As hosting of large scale server cluster (such as k8s cluster with thousands of servers).