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 Diana Plesa on May 09, 2006
ACID transactions don't work for long-lived use cases. This article documents historic approaches taken in the CORBA and J2EE communities toward extended transactions, how SOA is a more natural fit, and why WS-TX & WS-CAF may finally hold the answer.
Read: A History of Extended Transactions
Can we have a printer friendly link please ?
Sanjiv,
As it was stated in this article:
www.infoq.com/news/InfoQ-Unlaunched
the site is still in beta and aditional features (like those mentioned there, will follow soon).
Ahmed.
Thanks Ahmed. Indeed we have a long list of features on which we are working (and small fixes too :-) ).
./alex
--
.w( the_mindstorm )p.
InfoQ Chief Architect
Thanks for this great article! It's very useful, it has the right length and depth and the collection of references is much appreciated. Keep up the good work!
Use Firefox to browse to the article and save the page to your desktop, open that saved HTML page and print that. Format is nicer regards printing, and it's easy enough to throw away (recycle) the 'guff' (like my comment!) from the top and bottom of the print out.
Great article BTW!
That should work until the printer friendly links are in place.
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