3 ms·
There is some variance in how people interpret "cloud". Does colocating your own machine at a remote ISP constitute being in the "cloud"? What about leasing a
by kbenson 10y ago
There is some variance in how people interpret "cloud". Does colocating your own machine at a remote ISP constitute being in the "cloud"? What about leasing a server? What about a virtual server, but a traditional one where it's essentially no different than a single leased server? What if your multiple real and/or virtual leased servers are in the same private network at the remote location? What if there's an API available to you (even if it deploys hardware servers)? What if extra services, such as storage, can be attached?
Different people will likely consider "cloud computing" to apply at different thresholds with different features. I also consider "in the cloud" (handled remotely in the internet) to be different than "cloud computing" (handled by a cloud service), and "cloud services" to me could mean either one depending on context. I find most your statements apply truthfully to what I consider "in the cloud", that is, remote hosting. I don't think they necessarily apply when used with "cloud services" platforms. All of a sudden, all the money you save not having to deal with hardware and paying someone to configure and maintain it is either back (you need someone to deal with the craziness of each cloud services platform, and they might cost more), or offset by higher costs, if you don't have a business case that requires you be able to scale later, or add network storage, etc. Better yet, if all you need is a website, there's plenty of services that do away with all that to just provide hosting of various sizing and shapes. Is that a "cloud service"? Is that a cloud service? Probably, but in a conversation about GCE and AWS, maybe it's not actually what's being talked about.