4 ms·
> AWS is a terrible value once you’re paying the price of a bare metal box each year (or sooner!) You're probably off by about 2 orders of magnitude. If your
by bsder 6y ago
> AWS is a terrible value once you’re paying the price of a bare metal box each year (or sooner!)
You're probably off by about 2 orders of magnitude.
If your AWS spend is $10K per year or below, it simply isn't worth thinking about in terms of engineering time if you have real revenue.
Once your AWS spend crosses about $100K/year, it's time to pay attention. However, you probably want to be stingy about this as your engineer is in that range. Your engineers are supposed to be providing business value and looking at $10K/year costs probably isn't worth their time.
At the $1M/year mark, you already have an engineer on this full-time anyway so it makes sense to have some hardware you actually own in a colocation facility somewhere.
- josephg 6y agoI agree - but there's a few gotchas here. One is that there's often simple configuration changes where a few hours of engineering effort could save $30k+ each year, and those changes can still be worth looking into. I set up AWS a few years ago at a startup I worked at. I didn't really understand the difference between spot instances and reserved instances on EC2, and I didn't bother to learn (we were all very busy!). We didn't notice for 18 months or something, and the amount of money we wasted with that single mistake would have paid my salary for several months. Its also easy to accidentally lock yourself in to bad infrastructure decisions early, that become extremely expensive to fix later. Mongodb might seem like a good place to start your project, but trust me - moving away from it down the road will be a nightmare. Too much up front design will kill your velocity. And not enough up front design will cost you too. If there's a good rule of thumb here, I haven't found it yet.
- ramraj07 6y agoThanks for the honesty, most new engineers make such mistakes, AWS and other massive Cloud offerings are like a forest where one can easily get lost!
- bsder 6y ago> he amount of money we wasted with that single mistake would have paid my salary for several months. Sure. Presumably, though, your engineering salary for a couple months had more business value than you would have saved, so it's still a net plus. > Too much up front design will kill your velocity. And not enough up front design will cost you too. If there's a good rule of thumb here, I haven't found it yet. In my opinion, err on the side of velocity. Most startups are worrying about staying alive. If the startup survives to have the problem of ripping out bad decisions, consider that your engineering decisions did their job and chalk it up to the scars of battle. "Good judgement comes from experience. Experience comes from bad judgement."
- closeparen 6y agoNot sure how large the niche is where it makes sense to use “a” collocation facility - quickly you’re at a point where you should be thinking about multi region.
- demosito666 6y ago> At the $1M/year mark, you already have an engineer on this full-time anyway do you mean that for 100K/year you DON'T HAVE and engineer managing your account infra? Who does this in this case? CEO? This volume of spending implies quite an infra in AWS.
- pc86 6y agoNo they're saying at $1M/year it's one person's full-time job to manage your AWS (probably, unless it's dead simple and you're paying strictly for volume). It's unlikely you're paying an engineer $100-150k/yr to manage your $100k/yr AWS infrastructure full-time. More than likely at $100k/yr spend it's a piece of one person's job, or it's one of those things everyone on the team just sort of looks after.