I'll be the first to admit that I hadn't encountered the term "fog computing" before I read Andrew Froehlich's blog on Network Computing, but fog is something you might want to give thought to if you are involved in an Internet of Things initiative.
It's become kind of a best practice in deciding whether to launch a cloud-based initiative, including the move of an existing application to a cloud infrastructure. You are supposed to compare the costs and expected benefits of the cloud for infrastructure, IaaS, versus keeping applications on an internal IT infrastructure.
When you look at the cloud infrastructure market positions of Amazon, Microsoft, IBM, Google, and Salesforce, you could view the situation as the competition catching up with AWS or as AWS holding on to its lead.
It's an issue that pops up on a pretty regular basis here on The Enterprise Cloud Site. IT executives worry about where their service providers store customer data and where the providers' datacenters are located.
Many of us tend to think of the public cloud as that frivolous place where consumers hang out and that motley crew of rogue IT practitioners do their thing in the nether regions of the corporate world.
Two great myths are evident in the media today. First, people believe that the bizarre stories of the Kardashians and their lovers somehow represent reality. (Confession, I was stuck in a slow supermarket line today). Second is that restricting data storage to the turf and service providers of one's home nation ensures privacy.
There's the old saying that perception is reality. You know how it goes: Everyone believes a politician is a crook, so even if he isn't a crook, he has to move quickly to clean up his image before the next election. If consumers think a product is overpriced, the company has to do something about pricing.