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.
How would you like to view the presentation?
Early Access! Download JBoss Developer Studio 5.0 now, with packages for Mac, Windows or Linux!
Taming HTML5 and JS: High Performance Mobile, WebKit, FireFox Dev Tools @QCon New York
Big Data, Cloud & Mobile: Navigate the New Development Reality with Resources from IBM
You spend some time talking about the hash hack and then mention everyone using hashbang #! urls - but you specifically say that search engines won't work with them. You completely skip over the reason for the hashbang style taking over which is that google *can* crawl those urls if you properly set up support on your server for them. A simple google of "hashbang google" will point you to information on it such as this.
I understand why you'd want to gloss over this a little and emphasize the html5 alternative, but considering it isn't even implemented in the latest IE or safari (including iOS), you should maybe point out that its a viable intermediary solution.
Alright, sorry, I posted that before you got to the end where you sort of mention it. My bad.
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.
2 comments
Watch Thread Reply