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 Jonathan Allen on Oct 15, 2009
JavaScript is a language that is showing its age. A lot of developers now prefer to work with languages like Ruby or Python, falling back on JavaScript only for the browser. Sure there were attempts to support other languages in the browser like VBScript, but they never really took off.
Meanwhile, HTML is a rather poor languages for interactive applications. Sure there are Scalable Vector Graphics, but without support in Internet Explorer they are just as useless as VBScript. This has lead to the domination of component technologies like Flash, which are referenced by HTML but not used within it.
Gestalt is a JavaScript library that changes all that. Combined with Silverlight, Gestalt allows web developers to directly embed Python and Ruby code in their HTML. When you view the source of a site, you will see something very familiar:
<script language="python">
That, and an include at the top of the page, is all you need to start writing your code in Python. The include file pipes the inline Python or Ruby code to the Silverlight runtime, which leverages the Dynamic Language Runtime.
Gestalt, which is still just a demo, also allows you to embed XAML directly into the HTML. The XAML code is wrapped in an XML tag with the class attribute set to “xaml”.
According to Harry Pierson of Microsoft, this model of directly embedding Silverlight-compatible code in HTML is the eventual goal of the IronPython and IronRuby projects.
RDBMS to NoSQL: Managing the Transition
Automating Error Reporting for .NET Applications
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Troubleshoot Java/.NET performance while getting full visibility in production
How is JavaScript showing its age? Performance has increased as browsers improve their JavaScript engines. It supports some functional concepts and prototype style objects, and I'd say it's pretty close to parity with Ruby and Python in those regards.
Be sure to check out Jimmy Schementi's mailing list post detailing some of the work being done. He has some demos already posted, as well as some very useful documentation
I think the author means "age" in terms of language features rather than performance (as people have said Java and C/C++ are showing their "age").
Things like class/ inheritance model... String interpolation anyone? I would say "threading" but that's more an API thing.
Whatever happened to Google's "native code in the browser" concept that presumably would allow most JIT languages as well?
Also - its not really adding scripts to the browser, but to the silverlight plugin (which presumably lets you get at the dom). There have been lots of ways of doing that in the past but none have reached ubiquity.
HTML 5 looks nice and all, but there's issues with "just javascript".
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.
5 comments
Watch Thread Reply