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 Delap on Sep 28, 2006
The conversation started by discussing the history of FishEye. Moore stated that FishEye started as a part of their Crucible code review tool. They needed a durable way to reference assets under source control. The Java component that became FishEye was developed to solve need and shown to a few people including Atlassian's Mike Cannon-Brookes who commented "we'd buy this as it". Everyone that viewed the component responded that it was a product in its own right. As a result Crucible was put on hold and FishEye was born.
In terms of how customers are using FishEye Moore responded:
Cenqua also offers free FishEye hosting for Java.net projects in conjunction with Contegix.
It has been pretty well received. We use a lot of open source software ourselves, so we are more than happy to contribute something back. We now have about about 60 Java.net CVS project and even a couple of SVN projects. We can't mention FishEye hosting without a nod to the lads and lasses at Contegix who co-sponsor fisheye.cenqua.com and provide such excellent support.One of the more unique features of FishEye is the ability to query version control systems using a SQL like syntax called EyeQL. Moore elaborated:
EyeQL is the kind of feature that proves FishEye is driven by developers not marketers. It lets you write arbitrary complex queries that are really clumsy to do with a search form. It provides SQL like clauses with some syntactic sugar. Say you want a list of the tests you have modified between your "1.1" and "1.2" releases, you write:
select revisions from /your/module/This all gets that much more useful because you can do these queries via FishEye's API. A nice example of the integration possibilities using the API is the FishEye Plugin for Jira.
where (
path like "**/*Test.java" and
between tags (RELEASE_1.2, RELEASE_1.1]
and author = scott
)
return pathEyeQL like almost everything in FishEye is intended to be hackable, you can generate a URL in a build script or use CSV results as the source in an Excel spreadsheet. A few lines of your favorite scripting language will give you a command line repository grep.
Next Moore commented on some of the new feature version 1.2. Under the hood indexing and caching have been reworked allowing more features to easily be added in the future. Subtle use of Ajax has improved perceived page render times. Support for custom authentication plugins was also added due to customer requests.
Introducing SQLFire: a memory-optimized, high performance SQL database
RDBMS to NoSQL: Managing the Transition
Banking Case Study: Scaling with Low Latency using NewSQL
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
I just wanted to point out that we (Contegix and Cenqua) host FishEye for a hundred odd SourceForge projects and a few others too. See fisheye.cenqua.com if you want yours added.
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