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 Shane Hastie on Feb 28, 2011
In February it will be 10 years since a group of self-styled “anarchists” (their names and details can be found here) got together in Snowbird, Utah to discuss and debate their ideas on better ways to build software. The output from that weekend was the Agile Manifesto – the document that embodies much of the thinking behind the Agile movement today.
The manifesto is a set of four values and twelve principles that should guide software development teams in the way they work and interact with customers.
We are uncovering better ways of developing
software by doing it and helping others do it.Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
The Agile Alliance was formed out of that group and many of them have gone on to be the recognised gurus and big-names of the Agile community.
In 2001 Jim Highsmith and Martin Fowler, two of the original signatories, wrote an article explaining the motivation and thinking behind each of the values and principles that made it into the Manifesto. The original article can be found here, it is well worth reading:
In the last ten years Agile has gone from being a fringe idea to one of the most prevalent approaches in use today with over 35% of IT professionals saying that Agile is the way they work according to Forrester research.
To commemorate a decade of agility, InfoQ is running a series of articles; we have invited all of the original signatories to contribute along with others in the Agile community.
These articles are a snapshot of opinions and perspectives from the agile thought leaders.
This series will build up over the next couple of months, and will live on as a record of the state of agility in 2011, ten years into the agile era.
In addition to the articles in this series, this landing page will provide links to other sites and commentaries commemorating the anniversary. Be sure to check back here regularly for the latest content.
The articles in the series are listed below. This list will be updated as they are published.
A landing page has been established on the InfoQ site to bring together all the articles and news about the anniversary of the mainfesto together. It can be found here.
The Agile Alliance have anounced that most of the signatories will be reunited at Agile 2011 - see the anouncement here
Needless to say, InfoQ is not the only news organisation commemorating the anniversary. This page will also contain links to other events and publcations about the anniversary:
Shane Hastie is an agile coach, trainer and consultant working for Software Education in Australia & New Zealand
Agile Maturity Model Applied to Building and Releasing Software
How ALM Supports Business Processes
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
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