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 Al Tenhundfeld on Mar 11, 2009
neXpert is a Microsoft-sponsored add-on to the popular Fiddler web debugging proxy. neXpert extends Fiddler's performance testing capabilities and simplifies the process of finding performance issues in web applications. Version 1.0 was recently released and is available for download through Microsoft.
neXpert adds the following features:
neXpert can also create an HTML report with checks for common ASP.NET peformance issues. This report is useful as a diagnostic tool and can also serve as a deliverable artifact of development effort put towards optimization. The performance report checks for issues in the following areas:
For a quick tutorial on neXpert 1.0 and Fiddler in general, see MSDN Webcast: Web Performance Testing with Fiddler and neXpert (Level 200).
Troubleshoot Java/.NET performance while getting full visibility in production
Automating Error Reporting for .NET Applications
RDBMS to NoSQL: Managing the Transition
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Tutorial: Automating tests without compromising coverage of the environment
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