4 ms·
As a startup, owning hardware (or, sometimes, leasing) tends to eat up on your balance sheet really quickly as a cap ex (capital expenditure). You're immediatel
by imajes 17y ago
As a startup, owning hardware (or, sometimes, leasing) tends to eat up on your balance sheet really quickly as a cap ex (capital expenditure). You're immediately spending money and taking runway off the table and turning it into illiquid assets.
So sure, raw hardware you own in a rack somewhere is probably cheaper over 18 months. But then you're still stuck with it after 18 months (whereas you can just swap out for a larger sized ec2 in the space of a few minutes, whenever you want, without penalty).
Then again, unless you're buying a whole cage/closet you're probably paying the top whack fee anyhow, since data centers almost always deal with negotiating on the cage/closet level - anything smaller is typically not worth it to them. So you're paying full rate for your 2u box, and sitting on hardware that's depreciating.
Plus, to get into the good datacenters, the ones that have provable disaster recovery, multi homed bandwidth, power and cooling , you will need to prove your creditworthiness and such. But that's OK - you'll stake all you got to get a couple cheap servers hosted somewhere that won't go down (and if it did, be trivial to heal)
Finally: to the point about predictable usage lowering costs: amazon already does this, with reserved instances. You give them a heads up about what you're going to need over the coming year, they'll give you a discount.
If distributed, fail tolerant and instant deployable are three things that describe your startup, relying on your hardware to always work, that your sysop friend is always around and that you're on top of kernel bugs seems like a pretty fast way to fail.
On the other hand, offload all this to a company who's doing it anyhow, and you might find that you get to extend your runway, grow with your customers (who says it is bad to deploy more servers based on customer orders??) and get to focus on more interesting things, such as where to find the next beer. :)
- fierarul 17y ago> If distributed, fail tolerant and instant deployable are three things that describe your startup, relying on your hardware to always work, that your sysop friend is always around and that you're on top of kernel bugs seems like a pretty fast way to fail. Indeed, if you are a typical startup, then you either don't have the capital, the time or the knowledge to manage your own hardware. But at some point you should move into a hardware-owner category at least because it's the foundation on whatever your are building and you might want some control over that.