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 Scott Ambler on Jun 06, 2006
Pareto's rule, also known as the 80-20 rule, tells us that we can acheive 80% of the benefits from 20% of the software. Ron Jeffries examines the implications of this rule, showing that the return on investment (ROI) of building 80% of five systems is higher than the ROI of building 100% of a single system.
Realistically, it might not be possible to always start at the top 20%, but you very likely could stop with the top 30-40% if you were flexible. As we see in Examining BRUF, traditional teams would apparently be better off if they were to only attempt the top 55% of the functionality of a system as the other 45% proves to be a complete waste. The point is that Ron is presenting an argument that we should all take seriously.
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
How ALM Supports Business Processes
Adopting Git for the Enterprise: Risks and Considerations
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!
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