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 Jeevak Kasarkod on Aug 28, 2011
In an interview with SearchSOA, Richard Soley, CEO of the Object Management Group (OMG), explains the adoption patterns of cloud computing and SOA as an effect of hype cycles . For a major section of the interview he focuses on the financial and technical reasons for why cloud computing is more relevant for startups as compared to larger businesses and the state of cloud standards.
Soley believes that the hype around cloud computing is obscuring its true value just like the roller coaster ride SOA experienced in the last decade. He further states that after the disillusionment at the end of its hype cycle, SOA continues to be adopted by plenty of organizations. He corroborates this fact with the success of OMG's SOA consortium and it's continued work within the OMG's business ecology initiative. Here is his general observation on hype cycles:
If you ask if SOA has become mainstream, the answer is ''yes.'' One of the definitions of whether a standard becomes successful is when people don’t talk about it anymore and they just do it.
On similar lines he hopes that the hype around cloud computing does not affect its reputation as a great idea. However in its current avatar cloud computing has not yet addressed concerns around security, transformation of legacy systems and related interoperability standards to impact large business adoption . On the other hand the opex vs capex discussion makes it a game changer for startups. He says:
Since cloud computing is about moving capital costs to operating costs, it is a major paradigm shift for startups. They can startup, although they are capital poor, with little or no computing equipment. They can buy more access - elastically as they need it - to computing power on a cloud platform as they go.
There is another reason why cloud computing is more of a paradigm shift for startups than for bigger companies. The issue is the legacy. And it’s not just moving your legacy applications to the cloud - it’s how to integrate what’s running on public cloud with the computing resources that are still in your own shop.Apart from the absence of a majority of standards needed in this space to address the technical concerns around managing cloud implementations, no single cloud portability standard has emerged a winner. However the silver lining in his opinion is the creation of the Cloud Standards Customer Council, which is a group of end users, that is responsible for prioritizing and defining requirements for the cloud standard organizations such as OMG, The Open Group, the WWW consortium, IETF and DMTF.
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.
No comments
Watch Thread Reply