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 Kurt Christensen on Dec 18, 2007
The call for submissions has gone out to those interested in presenting at Agile 2008, which will be at the Sheraton Hotel in Toronto from August 4th to August 8th. Grigori Melnik, Program Chair of the Agile 2008 Conference, described the new submission process in this video.
The submission process was summarized this way in a press release from the Agile Alliance:
Following core agile principles, this year's program selection will incorporate an iterative feedback process for those submitting session proposals. All proposals will be made available for review by the Agile community, enabling presenters to receive feedback and modify their abstracts based on suggested improvements until the final deadline of Feb. 25, 2008.The submissions site (requires free registration) enables users to submit proposals, as well as review, rate and comment on others' proposals. The site contains descriptions of the various session types; Grigori elaborated on this for InfoQ, describing the different categories of submissions that the conference is seeking:
TutorialsIn keeping with this year's music festival metaphor, each submission must not only specify their type (above) but must be submitted to the appropriate "stage," whose "directors" and reviewers will decide the finalists after the Feb. 25th cutoff date, taking into account the public reviews. Here are the stages, with links to their descriptions:Tutorials are instructor-led interactive 90 or 180 minute classes designed to provide participants with practical knowledge they can use right away on Agile projects. Tutorials have clear learning objectives that focus on teaching specific skills or techniques.
Research Papers
Papers of two types are invited: a) original, finished scholarly research papers with significant portion of the content being new (these papers will undergo a scientifically rigorous peer-review and accepted papers are published in the proceedings), b) position papers to share research in progress (different criteria are used for reviewing and the papers are published in the companion).
Experience Reports
An experience report captures the story of a real agile project, summarizing what happened on the project and the key learning points. These reports allow practitioners to share their practical advice and guidance with other teams. They are published in the proceedings and contribute to the collective body of knowledge on agile methods. Experience report presentations are typically 30 min long.
Workshops
A workshop is an opportunity for conference attendees to learn from each other about a relevant topic, generate ideas that expand a new technique or practice, or brainstorm ideas for the next new "thing". The format might be a workshop, a peer-to-peer session, a goldfish bowl, a think tank, a simulation, or whatever creative idea you have to get people thinking and discussing. In a workshop, participants learn from each other, as well as from the session leader. Resulting knowledge is transferred to the larger community. Workshop summaries are published as post-proceedings on the conference site. Could be hands-on.
Talks
Presentations on non-commercial agile topics that do not fit into the categories of tutorial, workshop, experience report, or research.
Panels
A panel is a moderated discussion, in which small groups of experts present their positions and discuss them with each other and with the audience. Great panels engage panelists with contrasting opinions.
Demonstration
Showing a tool or technique.
Other
We will have a wildcard session type for other types of sessions. This is the place for experimenting with new ideas.
Vendor Presentation
Sponsored session.
| Main Stage | |
Chansons françaises Customers & Business Value Designing, Testing, and Thinking with Examples |
Agile Maturity Model Applied to Building and Releasing Software
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!
A couple of clarifications on the above text.
1. Where it says "submission site(requires free registration)" this is simply go to submissions.agile2008.org/ and click on Create New Account.
2. Where it says "it's frowned upon to review your own submission!" - it's not actually possible to frown on this because the submission system does not allow people to submit reviews on their own submissions - however, they can make comments on reviews and edit their submission in response to the review.
Hoping to get lots of session proposals from InfoQ members.
Best regards,
Rachel Davies
Agile2008 conference chair
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