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 Michael Stal on Jan 06, 2012
On January 4th, IBM announced, it is going to acquire the cloud and SOA integration service company Green Hat. Testing is one of the main challenges when developing cloud or SOA based applications. Buying Green Hat IBM hopes to offer more productive testing approaches for such types of large scale software systems. According to IBM, Green Hat will be integrated into IBM Rational Solution.
Green Hat was founded in 1996 with headquarters jointly located in London, UK, as well as in Wilmington, Delaware, USA. The company is describing its market focus as follows:
We know the differences in testing requirements associated with integration, BPM and governance platforms. Green Hat designs specific functionality and process into the solutions for each vendor to assure lifecycle coverage including unit, functional, integration, regression, performance, virtualized application and run time testing.
For that purpose, Green Hat is currently offering different products such as:
Green Hat claims to have a lot of experiences in testing solutions that use technologies from IBM, Microsoft, SAP, Software AG, Sonic, Tibco, and Oracle. It created the aforementioned product portfolio for supporting such large scale software development projects.
IBM’s Kristof Kloeckner, General Manager, IBM Rational explains the motivation behind the acquisition:
This acquisition extends IBM’s leadership in driving business agility and software quality by changing the way enterprises can manage software development cost, test cycle time and risk. Together, we offer the most complete solution available today for agile software development and testing, with flexible options such as the cloud. Green Hat’s application virtualization capabilities will help our customers accelerate their delivery of business critical software.
More detailed information on the deal is currently not available. Thus, it remains to be seen how Green Hat’s portfolio will be merged into that of IBM and help to boost customer productivity in terms of testing.
The days seem to remain cloudy, at least in the IT world.
In Chinese, we call the husband who is betrayed by his wife that ’he is wear a green hat'. :)
Why not name it Blue Hat...
That is really a nice metaphor. I bet (and hope), IBM did not know the Chinese meaning :-)
Good one on the metaphor.. I was just thinking about it. But on the other hand, time to see another company going to disappear into obscurity.
That's the truth.
I was attracted by the tile because I couldn't get it how can 'IBM be wearing a green hat'?
"wearing a green hat" made me immediately think of Edward De Bono's Six Thinking Hats
It is a thinking system where participants view a problem or a proposed solution with a distinct focus by symbolically wearing a hat. When you wear the green hat, you focus your attention on creative and imaginative solutions.
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.
5 comments
Watch Thread Reply