6 ms·
Second that, fond memories of using their service ages ago. First VMs I had was from them. They had very good documentation and everything was simple. Then I
by dmingod666 5y ago
Second that, fond memories of using their service ages ago.
First VMs I had was from them. They had very good documentation and everything was simple.
Then I was introduced to 'wall of text' as a service, AWS, and never looked back.
- no_wizard 5y agoWhy move to AWS if you’re happy with Linode? Genuine question
- abofh 5y agoNot OP, but I can answer - also was very happy with Linode for boxes, but there's a lot more than just boxes these days - queues, streaming, metrics, monitoring, containers, etc. Once an application moves from 'runs on a fixed number of boxes' to 'autoscaling, automatic healing/recovery and distributed databases', the overhead of DIY gets high (and I'm paid to do that!). My clients pay a fairly high premium for AWS because it allows them to move _faster_, not that it's _cheaper_.
- dielll 5y agoare you a devops or SRE?
- abofh 5y agoDepends on the day of the week - literally. For one client, I wear the devops hat, enabling developers, automating CI pipelines, etc. For another, my role is more "experience in the room", telling you 'no, you really don't want to do that, here's your risks, here's your tradeoffs, here's a better way'. The jobs both derive out of a very similar set of tools and expertise, it's typically the client that decides what hat I'm wearing.
- dmingod666 5y agoLinode was very limited in what you could do, from what I remember. They had good service and documentation and I just like it now cause, nostalgia. AWS is extremely flexible and very very feature rich compared to linode. At that point, AWS was considered about 10 years ahead of competition.