In my opinion, that approach sacrifices pretty much all the benefits that cloud proponents usually talk about, like only paying for what you actually use or scaling up and down on demand.
In fact, I'm not sure what the actual difference would be between Lightsail and a good dedicated hoster that provides backup and failover services.
- They could have much better service
- And bring down their expenses by at least half again
I used lightsail, and it's a terrible service.
It is very expensive (still) compared to other hosting providers.
And if your instance ever go out of memory, it become unresponsive for as long as you don't go manually restart it.
On other providers that I use, the OS would just "sacrifice child" (kill the process) and restart it.
It's not ideal, but much better than having to go there yourself to restart the whole thing.
And yes, I fully agree with you. In addition to the other disadvantages, Lightsail also shifts the burden of process monitoring and management onto you.
But somehow on lightsail (only), the machine just goes completely unresponsive instead.
Too many startups starts with Kubernetes, microservices putting a lot of engineering into infrastruture when they should worry about product market fit and simple server would just do fine.
For example, one of my companies is doing hosting and image delivery services for photographers. I started it on one dedicated server, and now 10+ years later it's running on 3 dedicated servers.
My hoster does backups and OS upgrades, so there was never any reason to go into the cloud. Except maybe, if I wanted to burn cash on slow performance ;)
It's important.
I've been looking for a job recently and my lack of experience with excitedly building expensive overly engineered big piles of stuff to do simple things is really hurting me.
When I suggest simple solutions proportional to the problem size people look at me like I'm some kind of simpleminded ninny.
And then when I describe working systems I've made using the approach on companies that exited north of 10 million, then they usually just think I'm a bullshitter.
10,000 users? Just do a simple lamp stack on a $10 month vps and don't code it like a moron, it's not hard. And it can be delegated to almost anyone, that's important for longevity. That's it, move on with life.
I've even offered to show logs, I mean, it's remarkably bad how hard it is to find work as a cost-cutting product-focused engineer, nobody wants that shit, really.
They want autoscale, prometheus, travis, blah blah blah... as fancy and crazy as possible, an empire of infrastructure instead of infrastructure for an empire... It's a damn cult.
I'm thinking about giving up and giving in. Maybe spend a month and drop $10,000 or whatever on a bunch of the tech just so I can talk about these things.
---
The second thing I'm constantly surprised by is how many obvious things are formalized with fancy names, math equations, papers, etc. Stuff I'd think like literally anyone with half a brain would do.
Recently I found out about "CRDT". Apparently I've been doing it for a decade... It's just super simple stuff wrapped in needless formalism, like back when design "patterns" were all the rage. I used to think "why is there a name for that?" it's such basic stuff.
So saying "dude, the emperor has no clothes, here, take my coat" - bad interview strategy and it's hard to rectify because there's like 50 naked emperors and silicon valley culture is on a constant rotating basis of seeing the nakedness of 5 of them and ignoring the other 45.
Maybe what I should do is just a couple throwaway interviews to focus on finding out the current fads and then be able to give the right cultural signals for the ones I actually want.
And it's been fine, profitable, revenue generating, sure. Mysql, php, a bit of python, easy stuff.
Honestly I've been wanting to move and try out silicon valley again though and it's been hard because I don't speak that language and frankly I'm skeptical and hostile to it - bad idea. That bad attitude needs to go.
I've been in practical startup land too long so I keep getting stonewalled from getting in to the sv world.
I'm trying to contribute to some companies open source projects recently and then basically earn my way in through labor since I can't do the virtue signaling. It's only been a few weeks, nothing yet.
I gotta learn how to be along for the ride without always trying to reach for the steering wheel.
Hopefully by the end of summer I'll find a lead somewhere.
It's not about the money, it's kinda actually how I want to spend my time for the next year or two.
> We are a team of two people
Articles like this reflect the fact that one size does not fit all.
> a good dedicated hoster that provides backup and failover services.
In theory that sounds reasonable. In practice the ability to completely manage the system via a web console and APIs makes a big difference.
https://wiki.hetzner.de/index.php/Robot_Webservice/en
But honestly, if you have only one server, what do you need an API for? It'll be much faster to just configure things by hand. It's not like you'll switch servers very often. Or at least the original article says that they committed to monthly cancelation terms.
That's a trope that I have never seen in practise.
A company might have some small percentage of clusters that autoscale, but usually there's a bunch of servers that don't.
Also, when AWS has control plane problems, autoscaling doesn't work, you get swamped, your health checks fail, and you lose all your servers and you're hosed. So it's better to always over-provision in the first place.