Linode Virtual Private Servers
Overall Satisfaction with Linode
I use Linode to be able to use Unix or strictly Unix-like operating systems (OS) on a powerful server for Internet sites. I am the 'organization' so is used by 'all.' Linode addresses the problem of access to powerful (yet affordable) servers usable for all normal Internet protocols, with high bandwidth, and with some protection against DDoS, supported by a team of experts in POSIX-based OS.
Pros
- Offers GNU/Linux distributions for servers.
- Offers loading your own .ISO for servers (such as *BSD Unix).
- High-technology (powerful system resources and network services/bandwidth).
- Helpful/friendly customer support.
Cons
- Should consider allowing/supporting *BSD & OpenSolaris/IllumOS Unixes in their choices of .ISOs.
- Should be a little more speedy updating non-systemd (real server) GNU/Linux .ISOs
- For the number of servers they administer, might consider enlarging their team, but their current customer support team is more than adequate.
- Increased server uptime.
- Probably increased viewers (higher bandwidth).
- Increased server efficiency (less space needed for non-graphical-user-interface, non-GUI, .ISO) than running my own hardware server (though you could run X Window System remotely on Linode.).
In terms and conditions, Linode has the most Constitutional terms on speech. The other simply didn't, especially if in Europe. If I wanted to criticize ideas, even if not criticizing people, then non-Constitutional terms of services simply weren't satisfactory. I did use one or two others for different reasons, like a friend's project (needed me to use that one) or connecting to software hosted there, but speech wasn't much an issue in those cases. Ease of use and accessibility were similar and not a serious issue.
Total cost of ownership isn't an issue/goal. I link shops on some websites and make small amount of income, but as they aren't for popular things (maybe even unpopular,) I put in more money than I make, which was expected beforehand. If I was doing it primarily to make money, and had popular subjects, good design, better ways of selling, I'm sure things would be going great because of sufficient server space, professional-level uptime (I've had fewer reboots than the number of years I've used Linode, even if I include personally-done system upgrades) and high bandwidth.
Infrastructure uptime is critical: I always want my Internet sites to be available, because I have thousands or more of interested people. People get directed to some of the sites anytime during the day/night, so there must be uptime at all hours. Whenever I had downtime because of hardware upgrades, it was something like a mere minute (projected) if not just few seconds (or whatever particular OS boot time is).
Using Linode
1 - owner/sysadmin/webmaster/scientist/designer
1 - computer science, possibly POSIX-based
- virtual private server
- webserver
- FTP server
Evaluating Linode and Competitors
Yes - home server. Heat issues, low bandwidth, not professional uptime.
- Product Features
- Product Usability
- Product Reputation
Uptime/bandwidth.
Might use low-range instead of mid-range VPS, but low-range might not be powerful enough.
Linode Implementation
- Implemented in-house
Yes - 1. Setup OS.
2. Setup firewall.
3. Setup webserver.
4. Setup FTP server.
5. Setup chat software.
6. (in-progress) Setup more world wide web (WWW) software.
2. Setup firewall.
3. Setup webserver.
4. Setup FTP server.
5. Setup chat software.
6. (in-progress) Setup more world wide web (WWW) software.
Change management was minimal
- Operating systems available from .ISOs already there.
Linode Support
Pros | Cons |
---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved Kept well informed No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response | None |
No. I'm already a higher academic computer scientist so can be my own sysadmin, and can't afford premium support.
Yes - It was more a configuration bug with the particular operating system (OS) I chose from Linode's .ISOs. The bugs were resolved to my satisfaction, and in a timely fashion.
Once it seemed my server was attacked/DDoSed. Linode seemed to take extra time to write extra detail of all options of what I could/should do and how, until the problem was resolved. Later I ended up also deciding to reinstall (for extra security) and add a firewall to prevent the same happening but they had already summarized how to do that without too much inconvenience, then were also available to give more detail before/at the time of the reinstall, and they have an article on firewall setup.
Using Linode
Pros | Cons |
---|---|
Like to use Relatively simple Well integrated Consistent Quick to learn Convenient Feel confident using | Difficult to use |
- Install virtual private servers (VPS).
- Setup VPS security.
- Manage account & VPSs.
- Find where you assign IP addresses to domains you have setup those IP addresses in DNS (at least was originally hard after the change).
Comments
Please log in to join the conversation