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 May 24, 2007
One of the most lauded features of HTML and JavaScript is how easy it makes it for hobbyists and novices to get started simply by looking at the source code for a feature they want to copy.
With Silverlight, viewing the source isn't as easy. Unlike JavaScript, Silverlight can send compiled assemblies to the client instead of the raw source code.
Fortunately, this isn't the end of the story. Using a technique called decompiling, Lutz Roeder's Reflector can turn these compiled assemblies back into code. While the resulting code isn't identical to the original source code, it is functionally the same. On the plus side, it doesn't have to be returned in the same language. This makes Reflector a pretty good language conversion tool.
In order to make viewing Silverlight assemblies easier, Ernie Booth has created a Reflector plug-in that downloads the correct assembles based on a URL.
Troubleshoot Java/.NET performance while getting full visibility in production
Automating Error Reporting for .NET Applications
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
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