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 Dilip Krishnan on Apr 29, 2009
In response to Joe Gregorio’s post, on why the browser is undermining the adoption of Atompub protocol, Sean McGrath, had an interesting take on the changing notion of what constitutes a web application.
Somewhere along the line, the "structured content+stylesheet=dynamically rendered page" equation broke down. Javascript began to flex its Turing Complete muscles and today we are staring down the barrel of a completely different concept of a web "page"...
According to him, the landscape of applications in the Web 2.0 era is changing; HTML is increasingly becoming a host to “applications”, delivered to the browser via the web.
… because HTML […] allows JavaScript payloads. But if 99% of my pages are 99% JavaScript and 1% declarative markup of content, am I serving out content or serving out programs?
He warns of the danger of a time when content will no longer be as freely available in the web, only to be replaced with “programs” that abstract the access to web-content as we know it. As to why AtomPub may not see much adoption, he believes that
When history is written, I think it will show that without the visual nature of the Web, it never would have taken off as an IT substrate.
He refers to Hugh Winkler's REST hypothesis, in which, Hugh suggests that the fundamental difference between the visual web and the “Atom applications” is that
…. the real, browser plus HTML web has, that RESTful systems don't, is the user agent. The human in front of her browser. An intelligence that reads and understands the meaning of "Author name" and "Title", and fills in an HTML form using queries against her personal database, stored in her brain. [Plus as a side benefit you also] get to present your own user interface.
Paul Fremantle’s post in response to Joe Gregorio’s post, likens the internet to an Anglican Church, and he sums it up saying that the internet is home to a diverse set of applications and protocols, of which AtomPub is just another player ...
[… and] any protocol that gets even a small market share of the Internet is a success. No protocol is ever going to take over the Internet, and there will always be plenty of different approaches to do the same thing. That is simply the nature of the Internet.
Is AtomPub really a failure? The relevant posts are available here, here and here.
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