Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Dilip Krishnan on Nov 02, 2011
In preparation for an panel discussion for a future of cloud computing event in Israel, Geva Perry a frequent speaker on cloud computing at corporations and industry events, published his predictions on the future of cloud computing.
[...] I wrote down a few of the concepts I've been thinking about for the past several years and I thought I would share them with my readers to get some feedback. Keep in mind these are long-term predicitions and trends (in no particular order).
As such cloud computing vendor offerings have different flavors depending on the services offering. Broadly services offered in the cloud are classified as Software as a Service, Platform as a Service and Infrastructure as a Service based on the solution stack. He predicts ...
He believes that there would be specialized clouds based on a number of factors. Different cloud platforms have different characteristics and so also, the applications that it supports. Not only are there various factors that are dictated by the nature of the business, but there are also regulations by various authorities, such as enterprises, banks and for that matter governments; privacy needs; and in general the performance characteristics. He asserts its not a one size fits all. In addition it brings up these questions about standardization, portability and the vendor ecosystem with his predictions.
We've highlighted some of the predictions from his original post. What do you think about these predictions?
Identity and Access Management for Cloud Apps: A Buyer's Guide
Modeling Your Cloud Services Brokerage
Want to know how software releases can be stress-free and happen with one click? Try Go free!
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
I predict that within the next few years, the hype around cloud computing will begin to fade and that a lot of these predictions (if not all) will seem very poor in hindsight. Cloud computing is surely an important but it seems more incremental than revolutionary to me.
I don't know if these predictions will seem poor or not in the future, but he makes good points based on what we know now. On the other hand I do think that many analysts are beginning to feel that cloud computing has matured enough that changes are beginning to feel incremental.
I don't know if these predictions will seem poor or not in the future, but he makes good points based on what we know now.
I'm not so sure. First of all, there aren't really any time frames. We can all make predictions that could eventually come true. It's predicting when that's the trick.
I get why PaaS is appealing to vendors (lock-in) but it's not terribly exiting for customers (lock-in). We tend to forget in technology is that people have to want what is being sold. PaaS only makes sense to the customer if it's standardized (of course a lot of IT customers are naive) but only proprietary PaaS is really compelling for the vendor. I find it unlikely that we will see one approach dominate the other. Additionally, PaaS requires that vendors retrofit existing applications. This is a pretty expensive thing to take for something that has little to no value to the customer.
The big problem with cloud computing as an industry is that if you have something where you can opaquely trade computing resources (as predicted) that means that none of the cloud providers have any real advantage over each other. They are just selling commodities. Not a really compelling business model. Sure you can talk about economies of scale but even this is questionable. Why is it cheaper per computer to run 10,000 computers than to run 1,000? The only economy of scale is getting full utilization which becomes harder the more computing power you have. It's not like 2 computers produce less heat or use less energy than one. And the more you pack computers into a space the harder it is to keep them cool, effectively limiting computer density. Even if big data centers provide efficiencies, they put more eggs in single basket so that disasters (natural or not) are more devastating. If a market environment, the smaller players may actually be more efficient. In an environment where computing time can be sold on markets, what's the barrier to entry?
Many of these predictions are mostly just lifted from the history of other industries or based on extremely short history of cloud computing. As the disclaimer goes: past performance is not an indication of future results.
We can all make predictions that could eventually come true. It's predicting when that's the trick.
:DThey are just selling commodities. Not a really compelling business model. Sure you can talk about economies of scale but even this is questionable.
Thats not the only thing, it serves needs that are not limited to that... for example its speed to market, scaling on demand, plus it arbitrages the added administrative/fixed costs. How efficiently providers deliver this solution is what sets them apart. In my opinion predictions, atleast in this case, are really an attempt to bring out these issues to the front.
The link James Urquhart is appreciated. I especially like this: to Data is not Electricity.
Actually, I think that perhaps the cloud computing model is better compared to an industry with huge capital costs where profitability depends on utilizing those resources. For example, it would have some parallels with the airline industry. In such industries, the biggest players don't always win. For example Southwest pummels the big-boys, not the other way around. Another similarity is that costs and therefore prices are highly dependent on energy costs and struggle to pass on such costs to customers. This is why companies are vying to place data centers near the cool breezes and cheap hydro-power of Niagara Falls instead of in the geologically unstable fire-trap California.
Bob's response to "Thinking Out Cloud's Predictions". Geva Perry is
an optimistic fellow and he came out with a list of predictions that
has been picked up at InfoQ (Thinking Out Cloud predictions).
Bob points out: "Predictions with out time-lines are fairly useless.
Cars will drive themselves. They will all be electric and many people
will own flying cars. As long as I never put a date on it, of course
it will very likely come true in the distant future."
He goes on to state: "No IaaS providers keep adding PaaS support and
the lines between IaaS and PaaS are fairly blurry. Plus you have all
of the not so great PaaS providers, who are not much more than window
dressing on AWS, over promising what equates to mostly to vaporware.
... IT shops are not jumping on the public cloud quite yet. There is
some trepidation there. Private clouds (on premises and off) and
hybrid clouds are going to see a lot more growth than pure public
plays. Public does not rule, and it will not rule for a while.
I could disagree about more, but I'll leave it for another day."
Thinking
Out Cloud: Predictions
Thinking
Out Cloud: Predictions, Bob's response.
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
6 comments
Watch Thread Reply