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.
How would you like to view the presentation?
Troubleshoot Java/.NET performance while getting full visibility in production
RDBMS to NoSQL: Managing the Transition
Branching & Merging Efficiently: A Guide to Using Process-Based Promotional Patterns
Combining Inspections, Static Analysis, Testing to Achieve >95% Defect Removal Efficiency
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Please provide a link to download presentation.
www.rationalsurvey.com/s/1059
11.7 Edit-Continue Not Working
When using runtime checking of contracts, the IL is rewritten by our tools. Edit-continue relies on being
able to insert code into an existing executable. Since that feature is not aware of the contract rewriting, it
won't work. There's no work-around other than not using edit-continue when also using contracts.
Hi Komal,
There were no slides for this presentation. It was a live demo and discussion.
Thanks!
Razvan
Greg certainly points this out but keep in mind that Visual Studio 2010 Professional (or lesser) can't use static checking. This is an exciting talk and will definitely motivate people to try this out. However, users with Professional can't take advantage of static checking. Hopefully Visual Studio 2012 or 2013 will resolve this ...
- John Wigger
I tried using Microsoft.VisualStudio.Tools.Applications.Contract.v10.0 in a VB.NET WPF project but I can't get the compiler to throw me compilation errors. Is there anything special we need to activate when using VB.NET? Or is it another library I should use?
Sorry, it is System.Diagnostics.Contract... No reference added... But still, it doesn't seem to work with VB. (I'm using VS premium)
It appears that 30% of questioned of 50 total(40 in survey and 10 in our team) uses Edit and Continue.
So using contracts prevents them from doing it.
Last time I checked it worked with VB, but badly. They didn't properly handle concepts like (If X = "" Then) meaning the same thing as (If string.IsNullOrEmpty(x)). That was over a year ago and they may have fixed it since.
Code contracts should be expressed declaratively as much as possible. It shouldn't require three lines of code just to say parameters x, y, and z cannot be null. Instead we should have attributes for all of the common cases.
The second problem is the utter lack of support for reflection. There is no way to programatically determine what contracts apply to the public API on a class.
The third problem is that it is an all or nothing proposition. Because contract violations crash the application you cannot safely mix contract and non-contract code in the same program. Had they choosen to use standard concepts such as ArgumentException and InvalidOperationException this wouldn't be a problem.
In short, the design of this is just plain wrong. They need to go back to square one and rethink how contracts should be expressed and enforced.
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.
9 comments
Watch Thread Reply