Attending Gigaom Structure was an exercise in getting fire-hosed with the leading edge innovation that public cloud providers are bringing to their customers worldwide. These innovations not only will have a profound effect on public cloud computing, but also will ultimately impact data center architectures, costs, and benefits worldwide.
Articles Tagged with Cloud Computing
We have all heard the hype that the cloud is the way forward in the twenty-first century, and I am sure you have heard the claim from cloud advocates that at some point 100% of computing will reside in the cloud. This seems logical, based on current trends and a quick glance over the announcements of new products and services released each and every day. But in all honesty, these cloud-based products and services are designed to work best when there is high-speed connectivity between the end user and the cloud.
Having twice been told by federal courts that the FCC does not have the authority to regulate the Internet in the same manner in which it regulates voice communications (that quaint POTS service that ran over phone lines), the FCC is now back with an attempt to impose net neutrality within the bounds defined by the courts.
There is an old saying, “the definition of insanity is to repeat the same thing over and over and expect a different result.” The way many enterprises are approaching the cloud, insanity would be a great way of classifying it. When we look across most enterprises, we see a collection of technologies from every era of computing. We have just about every vendor solution imaginable—often multiple versions of products from the same vendor—and a hodgepodge of architectures that makes spaghetti look organized.
For over a year now, a large number of industry experts have been asking questions like “is PaaS becoming just a feature of IaaS?,” “is PaaS dying?,” “do you really need a PaaS?,” and “is PaaS dead?” This has raised great deal of passionate debate in Twitter-land and other social media outlets, although supporters of stand-alone PaaS solutions are mostly those who are employed by vendors of those solutions.
One of the great advantages of the public cloud is its elasticity, the ability it gives systems to provision and deprovision resources as workloads increase and decrease. Much has been written about how building RESTful services is crucial to deploying elastic services in the cloud. I concur that writing code loosely coupled with the underlying infrastructure and abstracting things like business rules, business processes, and systems configurations into independent modules is a key to elasticity. What I have not seen discussed enough is how we should be abstracting the different types of server farms away from each other to eliminate tightly coupled dependencies between compute resources.