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 Jun 25, 2011
The experts of the software company EdgeCase have recently assisted the Enterprise Architecture Company Janova from Ohio in building a Web-based, automated testing tool. The tool is provided as a Cloud-based application that enables users to define the test scripts used for Batch Processing in plain English. For its implementation the developers leveraged the programming language Ruby.
It took the joint team consisting of Janova and EdgeCase software engineers only 8 months from the initial prototype to the full implementation. The three main ingredients for the development of Janova have been:
Those readers who are more interested in the internals and detailed use of Janova can access the forums site where tutorials, screencasts and other information is available.
Janova has also been recognized by the global media company Red Herring. An editorial team of Red Herring added Janova to its 2011 list of the Top 100 innovative companies in the US. According to Alex Vieux, CEO of Red Herring
After rigorous contemplation and discussion, we narrowed our list down from hundreds of candidates from across North America to the Top 100 Winners. We believe Janova embodies the vision, drive and innovation that define a successful entrepreneurial venture. Janova should be proud of its accomplishment, as the competition was very strong.
Customers can subscribe to the service for a monthly fee of US$ 10 per user and month (Basic Version) or US$ 25 per user and month (Professional Version). Janova also offers an Enterprise Version for testing unlimited numbers of applications and unlimited simultaneous test executions. In addition, it is possible to obtain a 15 days trial account.
Getting Started with REST: Free Cheat Sheet
Deliver quality code quicker with "Go" Agile release management
RDBMS to NoSQL: Managing the Transition
Tutorial: Automating tests without compromising coverage of the environment
Branching & Merging Efficiently: A Guide to Using Process-Based Promotional Patterns
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