IT Central Station is now PeerSpot: Here's why
Buyer's Guide
Infrastructure as a Service Clouds (IaaS)
July 2022
Get our free report covering Oracle, SAP, IBM, and other competitors of Google Compute Engine. Updated: July 2022.
620,987 professionals have used our research since 2012.

Read reviews of Google Compute Engine alternatives and competitors

Allister MacLeod - PeerSpot reviewer
DevOps Engineer at a computer software company with 11-50 employees
Real User
Top 5
Straightforward to set up, helpful support, and the Object Storage is useful for system backups
Pros and Cons
  • "The most valuable feature is the static IP address, which has been very helpful for being able to log into the same address over the course of more than a decade."
  • "I would like to see more seamless integration with backup, although it's pretty easy to do."

What is our primary use case?

I have a single 4GB model Linode and I use it as a personal server. I originally set it up to act as an email server, just for my own personal vanity domain. I don't use it for that anymore, but it's proved to be useful for many other things.

Right now, I run a Minecraft server on it and I also use it for a little bit of software development. I also use it as a jump host, if I need a stable place to SSH from my laptop to get to other online resources. It means that I only have a single point that I go through to get to the other stuff that I need.

How has it helped my organization?

I would say it's very important that Linode offers a relatively small, but well-focused set of cloud computing services because it differentiates them from AWS, Azure, and Google Cloud by being focused and by having a more personal touch. I could probably get the same compute power for a little bit less from other providers, but the value of the continuity and the high quality of support is worth it. It's rare that I need to reach out to support, but when I do, the support is great.

Even though I use it for personal use, some of the things that I use it for are in a software development capacity. For example, the ability to experiment with running my own Mercurial server, Git server, and source control servers on this machine have leveled up my own knowledge of those products in a way that I think a more managed solution wouldn't. Having the tools in-hand of just a Linux box that I can play with, and that I can wipe and reimage at will, is more useful than a physical machine by virtue of that virtual rewriting. It is also more useful than a more abstracted managed service, just in that I can get my hands dirty and do rapid experimentation.

Linode has helped me to accelerate innovation and even though I'm not using this in an enterprise way, it has improved the way I innovate with respect to personal stuff. For example, it has helped with the things that I'm trying to learn and the things that I'm trying to do. Setting up a Minecraft server is a good example of that. Being able to read some of the documentation that Linode has about setting up a Minecraft server on your VPS, and just learning and figuring stuff out, has been valuable.

What is most valuable?

The most valuable feature is the static IP address, which has been very helpful for being able to log into the same address over the course of more than a decade.

Another useful feature is being able to have multiple system images that I can play with. I mostly use Ubuntu Linux, but if I want to play with a new version of Ubuntu, I can pretty easily add that. It's been super useful to upgrade my system over the years.

I just recently started using the Object Storage and Backup features, as well. Having good backups for peace of mind and disaster recovery is very nice as well.

Object Storage has been key, for me. I don't have a strong notion of exactly when Linode introduced Object Storage, but it's been very useful for me, for instance, in backing up my Git server, in addition to the whole node backup. The fact that I can interact from the command line with the Linode Object service to back up specific datasets, is super cool. I know they didn't have it when I first started using Linode and I think it's been introduced fairly recently, within the last couple of years.

The Linode documentation is superb. 

What needs improvement?

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

Having more on-demand features would be helpful. For example, if for a little while I wanted to have four Linodes instead of just a single one, it seems like it's a little bit more difficult than spinning up an EC2 instance in AWS. It isn't a lot harder, but it could be improved nonetheless.

For how long have I used the solution?

I have been using Linode for more than a decade, since 2008 or 2009.

What do I think about the stability of the solution?

The stability is excellent. It's very rare that there is an interruption in the service. I think that the reboot notices that I get, that aren't related to me doing stuff, are less than one a year. I think, in some cases, it's been four or five years between needing to have any kind of stability-related events on the machine. I can't think of any outages in the entire course of me using it, that anything with any kind of significant impact.

Part of the thing that I value about the single Linode that I have is that it is a very steady, stable known quantity. I don't have to worry about all the institutional weight that I do with interacting with AWS, which I do a lot from work.

What do I think about the scalability of the solution?

Thinking about it from an operations point of view, I think that I would have a bit of a harder time scaling in Linode than I would in AWS, but not a whole lot harder. Given the Kubernetes support, I would imagine that that makes the process even easier. That said, I have not tried Kubernetes so I really have insufficient data to be sure.

It's not likely that I'm going to significantly increase my usage in the future. I might bump up to a higher size if I find that I need more CPU or RAM. Or, I might play around with having two to four Linode nodes. But beyond that, it's unlikely that I'm going to expand much.

I will definitely keep using Linode for as long as it is as stable and reasonably priced as it is, but at a steady one machine for my personal purposes.

How are customer service and technical support?

The support from Linode is great. All of the times that I've reached out, it's been through email or through the web portal. It's always felt good and it felt like the person responding understood what I was asking about and solved it very quickly.

In terms of flexibility and overall responsiveness, the support is very good to excellent. Certainly, everyone that I've interacted with, in the fairly rare occasions that I do need support, have been very knowledgeable about the product and very good at understanding what issues I'm having and how to solve them.

I would say compared to AWS, AWS support varies a lot in terms of responsiveness and whether you've got a paid support plan. Sometimes, it does take a fair bit of back-and-forth with AWS support to get to the crux of the problem. I've never felt that back-and-forth was as necessary, that we get to the crux of the problem and solve it much more quickly with Linode.

Which solution did I use previously and why did I switch?

Prior to using Linode, all of the machines that I had managed were all physical. I had my own personal machines and machines that I built for work, but they were all physical PCs or other architectures that I had to actually open up a case, and if I needed more RAM, I had to put the sticks in myself.

In comparison to a physical server, Linode has definitely saved me money. I never want to build a server again. Basically, if you build a physical machine and it is obsolete within two to five years, you've got to buy and recreate the whole thing again. Generally, the hardware is going to get cheaper over time, but I think that unless I were really putting a microscope on getting the cheapest components for building, Linode will cost less.

In some contexts, albeit not mine with just one or a few machines, it would make sense to build them. However, not having to worry about it and just letting Linode take care of the hardware upgrades is probably saving me money. I don't know if it would save a very tightly tuned hardware IT team money, but that's a completely different scale than what I'm looking at.

Linode was my first experience with virtual cloud servers and virtual machines, in general. Not too long after I started using Linode, I did start doing more with VMware, with an on-premises, physical server hosting multiple virtual machines. It was not too long after that when I got into AWS for work.

How was the initial setup?

I found the initial setup to be fairly straightforward. It's so long ago that the details are fuzzy but I recall that I set up the account, chose names for things, picked which size I wanted, and then launched it. Within, what at that time, was an astonishingly short amount of time, I was able to log into it. It's just gotten better from there.

I didn't require an implementation strategy, although I think that's peculiar to using it as a single thing for personal use. I had the notion that I wanted a persistent Linux machine that was always on, and that I could get to from anywhere, and Linode seemed to fit the bill.

Over the years, I've used it for a lot of different purposes and it's adapted well to that. So I would say in this case, I didn't need a whole lot of planning. If I were to use Linode for a more complex deployment, I would want to plan it out, figure out what the costs are, figure out the network topology, and the other relevant details.

What about the implementation team?

Linode offers worldwide coverage via multiple data centers, although I don't personally need that. It's a very attractive feature for sure, but since I just have the one virtual private server and it's just for me and for my friends connecting to it, I want it to be geographically close to me to have a low ping. I think it's located in New Jersey, and that's good for me, being in New England. While global coverage is not super important to me, in so far as it contributes to the health of Linode in general, I'm all for it.

What's my experience with pricing, setup cost, and licensing?

The pricing model is simple, and that's one of the reasons that I've stuck with Linode for so long. When I was on the $20 Linode, I knew for a fact that on the first of every month, my credit card would get charged $20. That meant my Linode was available constantly.

At this point, I'm paying more like $35 per month for a slightly bigger machine, and the backup, and the object service. But again, I know that it's exactly $35 every month and I can budget for it. The simplicity and the consistency of that billing and pricing are quite valuable to me. Whereas with AWS, it's a crapshoot. The on-demand pricing means it's flexible and I only pay for what I use, but it's also much less predictable.

It is tough to determine whether using Linode has saved me money compared to what I would pay with other cloud providers. I don't think it has on a pure numbers basis, but in opportunity cost and higher-level budget planning, I think that the consistency probably has saved me money. I would have spent more time trying things, allocating things that I might not need, and so on. Ultimately, it saved me capital in the long run but it is not necessarily something that I can put a dollar figure on.

In comparison to everything else, predictability is the key aspect of the pricing model. With it being a known quantity that I can budget for every month, it frees up brain cycles to do everything else.

Which other solutions did I evaluate?

In my personal capacity, at this point, I have my Linode and I have a personal AWS account, and I use them for different purposes, but to similar degrees, or similar magnitudes. I find that just looking at it from a strict CPU and RAM horsepower perspective, EC2 is just marginally cheaper, but there are different features that I value in different places.

I took a brief look at some other things like Azure, Google Cloud Engine, and DigitalOcean, and I found that when I was looking, and this was probably about five or six years ago, that a lot of things that I wanted were pretty comparable in terms of capabilities and pricing. A lot of it came down to what I valued, in terms of the positioning, and support, and documentation, where I very much like Linode's documentation, especially, and support.

Of the others that I evaluated, DigitalOcean seemed the friendliest. And then, AWS and Azure were the behemoths, the 800-pound gorillas in the room.

What other advice do I have?

The biggest lesson that I have learned from using Linode is the oldest lesson, which is just that a virtual cloud server has the availability and the flexibility that I couldn't get from physical at the time, or even now, for that matter. It's a key component in having something that's useful, having a machine that you can log into and do things on, in a consistent way, regardless of where I am or even what machine I'm connecting to it from.

My key advice for anybody who is looking into Linode would be just to dive right in. Pick it up and play around with it and if you find that it's not for you, try something else. But if you find that you love it, keep going.

In summary, Linode is a good product and I've been extremely satisfied with it for exactly the purposes I use it for. I have been pleased with it since I started using it.

I would rate this solution a ten out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
AlanGulle - PeerSpot reviewer
Advisory Board Member at Codecon VR
Real User
Top 5
Highly secure, fully integrated, and helpful support
Pros and Cons
  • "The application services are the most valuable in Microsoft Azure. I'm not using them directly but I am using the function and the web applications. I don't need to pay a lot for the maintenance. I do not need to have a DevOps employee."
  • "The documentation can be outdated and is not as clear in Microsoft Azure as it is in AWS or Google."

What is our primary use case?

We deploy all of our projects in Microsoft Azure. We are a startup company. We have been since the beginning deploying our code in Azure cloud. We are actively using the full capabilities of two cloud services.

What is most valuable?

The application services are the most valuable in Microsoft Azure. I'm not using them directly but I am using the function and the web applications. I don't need to pay a lot for the maintenance. I do not need to have a DevOps employee. 

I am familiar with Google, and everything I was doing was in Google. I had to control my back proxies and do my own configuration files. With Microsoft Azure, it is all easy.

What needs improvement?

The documentation can be outdated and is not as clear in Microsoft Azure as it is in AWS or Google.

For how long have I used the solution?

I have been using Microsoft Azure for approximately four years.

What do I think about the stability of the solution?

The solution is stable. 

It's easy to monitor, there's no problem with the code in their development. We had some stability issues, it was not the fault of Microsoft Azure, but it was the mistakes of the developers. It was easy to monitor it in Azure.

What do I think about the scalability of the solution?

Microsoft Azure is highly scalable.

On only one web application I created with one service plan I can connect 10  projects. Imagine one machine can run 10 projects at the same time because whatever the project has more requests or demands, it will scale its machines and auto-scale down. This is why it makes it affordable. I can control which project is demanding more computing power or storage power.

We have approximately 50 people using this solution in my organization. It is mainly back and front developers.

We are drastically increasing our usage because last year we were running 13 projects, and now 19 projects. In 2022 we are trying to double our team.

How are customer service and support?

The support could improve. For example, Python is needed for Microsoft Azure,  and the lack of documentation for the community is a problem. If you are a Python developer Microsoft Azure released an update to Python at the end of May 2021. Theoretically, I can use it with Python, but if I have a problem I need to call a Microsoft engineer to solve it. It takes some time. However, I did receive very good support from the Microsoft engineers to make my system production-ready, but language support for Python and other languages is coming late.

Which solution did I use previously and why did I switch?

I have used other solutions, such as Google and AWS.

When comparing these solutions to Microsoft Azure, AWS has better documentation, Google's cognitive services, and predictions give better results, and Microsoft Azure has the best UI. If you want to reach the database of Google, there is no such SQL manager UI. Microsoft Azure UI is easy to use and has great tools.

How was the initial setup?

The deployment's easy and the pipelines are easy from the Azure DevOps, everything is integrated and it has good security. The overall setup is extremely easy.

What about the implementation team?

We have a team in London that is maintaining the solution. We have 450 backend developers at this site and approximately five people are looking after all the maintenance and admin roles. We have database and developers administrators that are giving access to the people for the production maintenance. 

What other advice do I have?

I am very happy with the solution.

Thanks to the training I have received from Microsoft Azure, which cost £60,000, I'm up-skilling all my team for the certification, databases, and machine learning tool. Every month I'm receiving approximately £1,000 from the training credit for the up-skilling.

It is simple to start with Microsoft Azure if you know the application life cycle. You can try so many things without any cost because of the serverless system. You will not be charged for any request at the beginning. For example, you are creating a function application in Azure the first 10,000 requests are free. It is great because you can anyone a developer to test anything.

They're not using very heavy machine learning systems, the system is generally cheap. For example, they are giving a free month trial and a developer can't finish it personally if they do not use a large computing machine.

At the moment they are adding new features faster than I expected. For example, they have Python support but five years ago there wasn't any Python support. They were slow at the beginning but now it updates very quickly. For example, the community services for the low code, no code power platforms, and the power platforms.

I spoke to my developers, machine learning engineer, data engineer, and data scientists and told them please use the auto ML or the community services better. As a London business user site team, we can create all the virtual agents and AI builders with the no code platform for the machine learning models for the power applications. The auto ML is very powerful and you don't need to be an expert in machine learning.

I rate Microsoft Azure a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Karthikeyan Sivasamy - PeerSpot reviewer
Architect at a tech company with 201-500 employees
Vendor
Top 5Leaderboard
A easy initial setup with good dashboards and good documentation
Pros and Cons
  • "We don't run into any issues with bugs or glitches."
  • "The UX and UI could be improved on the AWS console."

What is our primary use case?

Lately, I've been using AWS Transcribe for transcriptions. I do have some videos that are a client requirement that convert meetings and videos into audio so that audio can be used as an input factor of the transcript can get transcribed.

What is most valuable?

AWS Transcribe is the most useful feature for us right now. It allows us to easily transcribe meetings and videos.

Overall, the solution has been very useful.

We don't run into any issues with bugs or glitches.

The customization is good.

We haven't had any security issues.

The solution offers very nice dashboards.

The initial setup is very easy. They offer good documentation, which helps the process along.

What needs improvement?

Currently, I can't think of any features that are lacking. It does everything we need it to right now.

The UX and UI could be improved on the AWS console.

For how long have I used the solution?

I've been using the solution for quite a long time. I started with it three years ago, now I think it's been more than two or three years at this point.

What do I think about the stability of the solution?

The solution is quite stable. I haven't had issues with bugs or glitches. It seems to be reliable.

What do I think about the scalability of the solution?

I pretty much just use the solution for my own personal learning only. I'm currently working on ten projects. There is also a client that I'm working with. They will be buying their own AWS console and they'll be using it. I might just scale them out with it. 

Therefore, I haven't tried scaling yet. I may be trying to scale in a month or so.

I do plan to increase usage and take on more projects in the future.

How are customer service and technical support?

I really haven't dealt too much with technical support. Mostly, I've been able to use their existing documentation to get the help I need if I run into any issues.

How was the initial setup?

The initial setup is not complex. We found the implementation to be very straightforward and simple.

The product has very good documentation which I was able to access. It's on AWS and it helps us with aspects of the setup and troubleshooting.

The solution requires very little maintenance.

What about the implementation team?

I handled the implementation myself. I didn't need the assistance of a reseller or consultant.

What's my experience with pricing, setup cost, and licensing?

I looked into various cloud services, and I found the pricing to be all pretty much the same AWS is pretty standard industry pricing.

Which other solutions did I evaluate?

I did look at Googe and Azure before ultimately choosing AWS which seemed to fit my requirements a bit better.

What other advice do I have?

I'm an AWS partner.

I'm using the latest version of the solution at this time.

I just come to our AWS console and I can look for new releases. I do some quick demo's and I try to understand what the releases are all about. I might keep findings for two or three months.

I'd recommend the solution to others. Their technology is top-notch.

I'd rate the solution at an eight out of ten. Although when I first started using it, I wasn't the biggest fan, I've found it's met all of my requirements nicely.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Infrastructure as a Service Clouds (IaaS)
July 2022
Get our free report covering Oracle, SAP, IBM, and other competitors of Google Compute Engine. Updated: July 2022.
620,987 professionals have used our research since 2012.