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 Michael Stal on Nov 02, 2011
Since 1990 Dr. Dobb’s Jolt Product Excellence Awards are awarded annually to representatives of the software industry in five different categories. Recently, on October 26th, The Jolt Judges announced the awards for 2011 in the category “Design, Planning, and Architecture Tools”. In detail, the Jolt hall of fame now includes the products Paradigm for UML, Restructure 101, and Requirements Center 2010.
To obtain the prestigious award in 2011 tools must reveal various properties. For instance, they should be more lightweight than in the past, easy to use, as well as easy to configure with respect to the needs of an organization instead of enforcing their own processes and methodologies.
According to the judges:
The winners of this year's Jolt awards are ideal tools in this respect. They're easy-to-use, complete, and integrate well with other tools, especially development environments. As a result, they bridge the no man's land between the requirements/design and coding stages, leading to the type of collaboration that enhances the development process systemically.
Requirements Center 2010 by Blueprint Software Systems, Inc. received one of the productivity awards. The tool automatically reflects all changes in the use case model, the business processes, or the requirements in the requirements model. It offers sophisticated editors and allows exports to ALM tools.
Headway Software got a productivity award for their product Restructure 101 which supports architectural refactoring. Using the tool architects can identify architectural smells such as dependency cycles in Java or .NET implementations. Restructure101 also includes metrics such as Cyclomatic Complexity for this purpose.
Another Jolt award went to Visual Paradigm International for their product Visual Paradigm for UML which already received a Jolt productivity award in 2004. The modeling tool was awarded due to its completeness and robustness as a designer toolbox. According to Gary Pollice,
It hits the sweet spot for software developers who desire a robust UML modeling tool, but want the freedom to use as little or as much formality as they need.
By the way, for all of you who always wondered what the name of the award means. “Jolt” does not define a four letter acronym, but refers to the sponsor of the award presentation, Jolt Cola.
In the next weeks the Jolt Award for coding tools is underway. If you like to nominate a tool just visit the nomination site.
How ALM Drives Business/IT Alignment, Competitive Advantage
Systems Engineering for Dummies eBook
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Learn how Application Lifecycle Management can support your business processes in this exclusive presentation by David Chappell.
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