5 ms·
All services should eventually be like this. Just as you don't want to deal with provisioning BTUs of air conditioning or watts of power needed for your cloud i
by biot 12y ago
All services should eventually be like this. Just as you don't want to deal with provisioning BTUs of air conditioning or watts of power needed for your cloud infrastructure, why should you concern yourself about allocating a certain number of bytes of storage?
- pyre 12y ago> Just as you don't want to deal with provisioning BTUs of air conditioning or watts of power needed for your cloud infrastructure Maybe you don't want to, but there is definitely someone out there dealing with these issues. E.g. during a heat-wave (100 F+) a transformer on top of the building (at a previous employer) started on fire. When the dust settled, we found out that the person in charge of it had not upgraded it as our power requirements increased. It was over-taxed and the heat-wave put it over the edge.
- tlrobinson 12y agoRight... which is why software should do it automatically.
- discodave 12y agoThat is a reasonable analogy but the question is whether or not your in-house support will do a better job than Amazon.
- toomuchtodo 12y ago> All services should eventually be like this. Just as you don't want to deal with provisioning BTUs of air conditioning or watts of power needed for your cloud infrastructure, why should you concern yourself about allocating a certain number of bytes of storage? Infrastructure guy here. Abstraction is to reduce workload; you still need to understand the underlying concepts. Otherwise, you're just the guy who freaks out when their DB is at 100% CPU utilization or hours of replica lag without knowing why.