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 Jonathan Allen on Mar 03, 2008
The Add-In Framework, introduced in .NET 3.5, is designed to facilitate applications that need to support partially trusted add-ins. It includes features such discovering compatible add-ins, segregating them into separate AppDomains, and handling the communication between them and the host application. It even supports unloading code without having to restart the application.
Unfortunately the framework is rather complex. Even the simple example on CLR Inside Out took a total of 7 assemblies in order to build even the simplest application. Most of this is just boiler-plate code used to define the various contracts, adapters, and views needed to make everything work.
If this was written for Java, one would start looking for things like XML descriptor files to lighten the burden. But in true .NET fashion, we instead turn to code generators built into the IDE. In this case, the IDE add-in is the Pipeline Builder for Visual Studio 2008.
The Pipeline Builder is still in a pre-release state and at this time it only supports C#. Fortunately projects that use the Pipeline Builder don't take on any extra dependencies, making it suitable for production use.
The source code, written with VS 2005, is available on CodePlex.
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Troubleshoot Java/.NET performance while getting full visibility in production
RDBMS to NoSQL: Managing the Transition
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