But the cloud IS someone else's computer. I don't own it. So if I put my data in the public cloud then by definition it is on someone else's computer.
You can extol and iterate the virtues as much as you want. You can provide guarantees and demonstrate all sorts of benefits. In the end, the general cloud computing environment is still not yours: it is someone else's computer. Even if you are renting it.
Which is fine. Sometimes that is good. Sometimes not so good. Sometimes you want the flexibility of spinning up a few hundred or thousand hours of server time on machines you don't have to own. Other times you want a private cloud.
I've worked several projects where a private on-site cloud was significantly cheaper to operate than a public cloud. The in/out costs smashed the cloud savings. Flip side, a project needed to be able to rapidly spin up machines as needed from a template, public cloud was the only way.
I think the phrase 'the cloud is not your computer' is actually useful, since literally it is true and forces people to consider that they should be careful with data management since all that data stored on the cloud is being managed by a third party.
And now there's "serverless" (which I don't fully understand), and now will there be "internetless" apps that use the internet too? Maybe "userless" apps are next?
I think we've reached peak hype through sociopoliticoeconomic circumstances, so now words' meanings have come unmoored and subject to seemingly arbitrary increased tectonic drift. For all we know, Chinese may rapidly supplant English soon and be the lingua franca fallback language for a while until dying out as did common Latin with the decline of the Roman Republic then Roman Empire, only remaining as fragments and loan words like fossils in other languages.
The cloud may not be just someone’s else’s computer, but someone else’s computer (and other material) is certainly involved. When my career began, the word we used was “outsourcing”.
There are advantages and disadvantages to outsourcing, or to using the cloud, and a cost benefits analysis needs to be done on a case by case basis. I don’t believe that’s changed much over the last thirty or so years, although the details regarding the exact pros and cons has certainly changed.
If you're talking to someone who is more technical then they'd probably appreciate a more thorough breakdown of what the 'cloud' is.
When my mom (who isn't very technical) asks what the 'cloud' is I'm going to say "Someone else's computer" because she doesn't care about controllers, servers, disk shelves, fabrics, etc., she just wants a general idea of what it is.
Another example of how some tech writers should work consumer IT for a while just to understand how little most people know or care to know.
> The simplest definition of cloud is a data centre that's full of identical hardware that no-one ever touches except to unpack it on day one and throw it away when it fails;
The hardware, yes.
> in between, every deployment, update, investigation, and management process is automated.
Well, that's simple not true. Maybe most if it is automated but not every.
And the thing that the author doesn't understand is that I don't own the hardware, I don't ownbthe software and I don't own the data that's in the server, even if the data is about me.
It is almost like renting an apartment but every furniture I buy and put in it becames property of the apartment owner and I only have some pseudo-rights about them.
6 comments
[ 3.3 ms ] story [ 26.7 ms ] threadYou can extol and iterate the virtues as much as you want. You can provide guarantees and demonstrate all sorts of benefits. In the end, the general cloud computing environment is still not yours: it is someone else's computer. Even if you are renting it.
Which is fine. Sometimes that is good. Sometimes not so good. Sometimes you want the flexibility of spinning up a few hundred or thousand hours of server time on machines you don't have to own. Other times you want a private cloud.
I've worked several projects where a private on-site cloud was significantly cheaper to operate than a public cloud. The in/out costs smashed the cloud savings. Flip side, a project needed to be able to rapidly spin up machines as needed from a template, public cloud was the only way.
I think we've reached peak hype through sociopoliticoeconomic circumstances, so now words' meanings have come unmoored and subject to seemingly arbitrary increased tectonic drift. For all we know, Chinese may rapidly supplant English soon and be the lingua franca fallback language for a while until dying out as did common Latin with the decline of the Roman Republic then Roman Empire, only remaining as fragments and loan words like fossils in other languages.
There are advantages and disadvantages to outsourcing, or to using the cloud, and a cost benefits analysis needs to be done on a case by case basis. I don’t believe that’s changed much over the last thirty or so years, although the details regarding the exact pros and cons has certainly changed.
When my mom (who isn't very technical) asks what the 'cloud' is I'm going to say "Someone else's computer" because she doesn't care about controllers, servers, disk shelves, fabrics, etc., she just wants a general idea of what it is.
Another example of how some tech writers should work consumer IT for a while just to understand how little most people know or care to know.
The hardware, yes.
> in between, every deployment, update, investigation, and management process is automated.
Well, that's simple not true. Maybe most if it is automated but not every.
And the thing that the author doesn't understand is that I don't own the hardware, I don't ownbthe software and I don't own the data that's in the server, even if the data is about me.
It is almost like renting an apartment but every furniture I buy and put in it becames property of the apartment owner and I only have some pseudo-rights about them.