yte15
Linode and Slicehost were very similar stories, though. Slicehost bootstrapped as well and was run by good people.
At the time Linode had a host-side scrub daemon that simply ate LVs as customers deleted. It’s technically simple, but drive longevity and capacity on the host (the user is probably recreating their VM, for example) is where it gets tricky. External considerations. In the end scrubbing is basically killing a few dozen inodes of user data, but the architecture in VPS usually requires you to nuke the whole image, including what is ultimately the host’s 59th copy of Ubuntu. Just managing the iops without annoying neighboring customers is a challenge.
To my cloning point I made at the top of the thread, Linode was certainly no stranger to the reality distortion field when it suited, and I think that’s yet another thing DO copied. That vertical is closer to B2C since you’re usually dealing with individuals, not sales teams, and glossing over stuff is a bit easier than when your counterparty has a better engineering team than you.
It’s a tough problem to deal with and not something you’re likely to think of designing such a product from first principles. That’s not an indictment, it’s just fundamental to experience gained doing this stuff (and it’s perilous to get wrong). Filtering unsolicited ARP to prevent domUs from hijacking default gateways was another lesson in blood, and one of the first things we tried within five minutes when we did competitive on DO around launch time (they hadn’t thought of it; it worked).