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?
Taming HTML5 and JS: High Performance Mobile, WebKit, FireFox Dev Tools @QCon New York
Early Access! Download JBoss Developer Studio 5.0 now, with packages for Mac, Windows or Linux!
Building HTML5 Apps in Hours, Not Days
Tools to unit test your JavaScript
Introducing SQLFire: a memory-optimized, high performance SQL database
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
Is there a problem watching the video. I am not able to watch it.
Hi Praveen,
This might be caused by a missing update of the Flash player. Please check on that and let me know if it works.
Thanks!
Razvan.
Can't download the mp3 version either - it says 'missing resource' ???
Refreshed page and then the download worked :)
I don't think it's a good idea for Java EE 7 just to be about the cloud. Majority of EE applications are NOT in the cloud and may have no intention to go there. We need productivity enhancements to the all the core APIs (jpa, jsf, ejb, jax-rs, etc.) We need to take a close look at competing platforms and see what's going on there. For example, Microsoft has a really nice new standard view technology called Razor and now a really nice MVC framework with tooling support. What about things like new strongly typed view technology to replace JSP? How about making security easier to work with(ever try creating a simple login backed by a custom user data store? Maybe JAAS needs to become ALOT easier to use.)
If there are only a few enhancements to the core APIs then we are stuck with what's in EE for many years to come (not that EE 6 doesn't have some nice things, but we need to continuously move the platform forward from all perspectives, especially on ease of use!).
The point about the cloud move is is one of the main themes of EE 7, rather than the only thing that is happening. Updates to APIs are planned. We'll try and get a round-up of know plans done shortly. There's also an interview I did with Jerome at QCon London - www.infoq.com/interviews/jerome-dochez-ee7 - which is worth a look if you've not seen it already.
We need productivity enhancements to the all the core APIs (jpa, jsf, ejb, jax-rs, etc.) We need to take a close look at competing platforms and see what's going on there. For example, Microsoft has a really nice new standard view technology called Razor and now a really nice MVC framework with tooling support. What about things like new strongly typed view technology to replace JSP?
Same feeling here :
* Add a standardised MVC framework (just copying .Net MVC and Razor will be fine). JSF is ok for internal sites, but it's really bad when it comes to sites with high throughput or when we need to do progressive javascript.
* enhance existing specs with hot deployment (JPA / CDI / JSF, ...) like JRebel or the playframework : 'Edit your Java files, save, refresh your browser and see the results immediately! '
* and perhaps enhance annotation scanning (use the only one scanning for all specs : JPA, JAX-WS, CDI, JSF).
* unify everything around CDI.
Cannot download mp3
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.
8 comments
Watch Thread Reply