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 Dec 05, 2007
Dialogs have always been a hobgoblin in the Windows platform. Developers are constantly faced with an unacceptable choice. One option is to use the built-in dialog and pretend Ok/Cancel or Yes/No are really appropriate prompts for the user. The other is to create their own dialog from scratch, which seems like a waste of time for what should be a simple prompt.
Windows Vista addressed this with the Task Dialog. This dialog provides a framework that covers most dialog scenarios while maintaining consistency across applications. But it also introduces a new problem in that it is not backwards compatible with Windows XP.
Hedley Muscroft tackled this problem by creating a wrapper/emulator for the Task Dialog. When running on Windows XP, the application will use his hand-rolled clone which supports most of the Task Dialog functionality. On Vista, it automatically switches to the built-in dialog.
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