Re: Public cloud barriers
Okay, I need to print 4TB of high-resolution photographs per day at my photolab on printers the size of cars. Please explain how I am going to run all my servers in the cloud and stream the images I need back to my photolab. Consider that the lab in question probably clears about $5M a year and wobbles on the edge of profitability as is. It can't afford a bigger pipe than it has now. What magic do you use to make this work?
Now, let's look at my machinist shop which has the same sort of requirements; data that must be delivered to local equipment in a timely manner from the cloud. The next-generation stuff does a closed-loop between the manufacturing equipment, sensors and analysis software which needs ultra-low-latency in order function properly. Am I going to run all of that in the cloud?
I also have bakery that falls into a similar category. These folks do a million samples a second from their sensors across the whole of the factory then crunch that data in real-time and feed the results back to the machinery for real-time modifications of the environment. Are you going to do that all in the cloud?
I have remote drilling teams that are doing real-time seismological analysis, modelling and simulation based on feedback they receive from on-site sensors. This information helps them decide where to drill, how and when. Their access to the internet is via an orbiting dirigible with an LTE booster. Are you going to put their workloads all in the cloud?
I have a storm chaser that collects over 50 billion samples a minute from over 1000 sensors and crunches that in real time to determine how storms are going to evolve. He is often driving between mountains where even cellular signals won't reach and satellite is thready to the fact that he drives into tornadoes for a living. Are you going to put his workload into the cloud?
I have a journalist that deals with Chinese dissidents, pursues human rights violations by the American government and is currently trying to uncover some unspeakable horror in Burma. Even if you could put all his workloads in the cloud, would you?
I have a fire hall that absolutely has to have the diagnostics and maintenance systems for their equipment running 60/60/24/7/356, no exceptions. They need 100% uptime and access to a number of emergency systems and are increasingly using sensors ranging from deepscan sonar to thermal sense drones to determine safety. Are you going to put their workloads in the cloud?
I could go on and on and on, but suffice it to say you're talking utter fucking bullshit. Some workloads can be put into the cloud because they have no localized mission criticality. Some workloads absolutely can not. Even for SMBs - like my 10 man bakery - there are workloads that will run local and some that could be moved to the cloud.
But the cloud is a tricksy thing. If I have workloads that I must run local - and despite your propaganda this will always be a truth of the world - then I have a floor cost of investment in local IT that I must make. If I am already balls-in on some local IT, then the question becomes "do I have the spare capacity on my local setup to run $_workload or not?"
If I have the spare capacity to run $_workload locally I do. Period. It will be cheaper to do so than farming it out to the cloud. If I don't have the spare capacity to run it locally then I ask myself the next question "what is the cost of running this locally versus the cost of running it in the cloud?" I already have local systems, local nerd and the rest...if the TCO of adding that workload locally is lower than farming it out, it gets added locally.
The cloud is great for DR. That way I don't need to light up a DR site. Provided, of course, that everything is encrypted at rest as well as in flight, and that data sovereignty issues are dealt with. And that I can download the data to my local network - where it will inevitably reside once I light my factory back up - in a quick and financially painless manner.
Some workloads that are finicky and irritating, but not especially mission-critical - like email, instant messaging and so forth - I have no problems putting into the cloud. The world doesn't end if e-mail stops for a day or two because Amazon blew up. My company does stop working if the delicate dance of complex sensor-analysis interactions with the bakery machinery ceases.
And if I can't get the fire alarm notice, why then...people die>.
How about you get "off message" for a little while, stop thinking like a marketdroid and start thinking about the human impact of cloud computing. The cost in lost profits from downtime, the cost in jobs from lost profits or shuttered businesses and the cost in lives if some things go wrong.
Then tell me, with a straight face, that the future is to have all workloads in the cloud. Because if you can actually do so you are going on the blacklist of "IT professionals" that I will never, ever deal with...and association whit you wilt be the viral touch of death for any contracts, vendors and so forth that I deal whit in the future.
You have a whole great big box full of tools at your disposal. Don't keep using a hammer for everything because it's what you have in your hand at the moment.