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 James Vastbinder on Dec 20, 2007
In this QCon exclusive presentation, Kevin Jones talks about Visual Studio Team System and how to customize other software methodologies beyond MSF. He covers project management, source code control, class designers and various designers available to software architects.
With the Microsoft Solutions Framework 4.0, Microsoft intends to provide a meta-model for software development lifecycle methodologies. The intent with VSTS is to provide a toolset that is both flexible and able to provide structure to the software development process.
Kevin provides a solid overview of VSTS and MSF usage. He touches lightly on the more popular agile methodologies like Scrum and there is active debate if VSTS can truly support such Agile methodologies.
What are your thoughts?
Automating Error Reporting for .NET Applications
How ALM Supports Business Processes
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Learn how Application Lifecycle Management can support your business processes in this exclusive presentation by David Chappell.
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