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 Apr 04, 2007
Jason insisted that I remove Express SKU support because allegedly I was in violation of Microsoft's license agreements and copyrights. He refused to give any indication of where or even which license I was in violation of! I was also barred from joining VSIP until I gave in to their demands. This meant I wouldn't have been able to get a PLK to release some unrelated functionality that I had been working on.These are serious allegations and consequences. Surely it is reasonable to request some indication of where I was in violation. If I was accidentally in violation then, how could I be sure not to end up in a similar situation in future?At one point Jason recommended I make an announcement on my website that was in contradiction to everything I had been saying and believed. If I had made this announcement and removed Express SKU support, I suspect my actions would have been deemed acceptable.
It wasn't the MVP issue that persuaded me to drop support for Express. Microsoft made it very clear that I wouldn't be accepted into the VSIP program unless I dropped support for the Express SKU.Unfortunately the only way to get a PLK (package load key) is by joining VSIP. If I was barred from joining VSIP then I wouldn't be able to release some functionality that I had been working on. For the moment I have decided not to join VSIP, however I do need to keep the option open.This is what Jason said:"As we have discussed on multiple occasions your hacks to integrate TestDriven.Net into Visual Studio 2005 Express violate Microsoft license terms and we ask that you stop distributing these hacks.""You will not be accepted into the VSIP program until you conform to our license agreements."I was never told where I was in violation of the license. Instead I got:"Microsoft can't provide you legal advice. You will need to work with your legal council to answer these questions."What could I do?
Using ALM to Drive Business/IT Alignment
Automating Error Reporting for .NET Applications
How ALM Supports Business Processes
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Combining Inspections, Static Analysis, Testing to Achieve >95% Defect Removal Efficiency
This is why I have chosen that my next computer will be a Mac or Dell with Linux. I'm of the firm belief that the only way to get M$ to stop strong arming people, businesses, and organizations is to just stop using their products. All the software, development tools, and visual eye candy that is available on M$ is available on other OS's. The only difference being is that some of the apps will be from a different vendor, and you will likely get better support, fewer dirty tricks, and better stability/security.
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.
1 comment
Watch Thread Reply