3 ms·
Yes, different situations require different solutions. I think most people learn this by the time they reach puberty. If you're trying to reduce costs on a com
by rhizome 5y ago
Yes, different situations require different solutions. I think most people learn this by the time they reach puberty.
If you're trying to reduce costs on a complicated usage pattern, then you'll probably want to have someone on staff or consultant who knows how to deal with those things.
I don't know your experience, but bare metal has at least an order of magnitude greater efficiency at one or two magnitudes lower cost. If you want to pay $1MM/mo for something that could also be done for (generously) $20K/mo (plus a couplefew salaries that add up to much less than $1MM/mo), that's your business, but I don't see how the use-case you describe requires cloud/AWS.
The thing that people don't get (or have forgotten, or...) is that you don't have to spin up hundreds of instances in the way you do on AWS, you just handle them on a machine or three that already has enough headroom to handle them.
(all hypothetical blather shaped to support my perspective and disprove the utility of yours, of course ;)
- dvaun 5y ago> Yes, different situations require different solutions. I think most people learn this by the time they reach puberty. Not so sure about most people learning this...though, I will say I'm probably a late bloomer compared to most on HN :) What you state makes sense. I think my tone was dismissive of the idea that running your own machines is worthwhile. To add to that, I haven't (yet) worked on large-scale systems so my comment is purely speculation.