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 Alex Blewitt on Apr 08, 2009
Google have released the Google Plugin for Eclipse, which supports both Google Web Toolkit and Google App Engine development, with tighter integration than the standard Java environment.
Google Web Toolkit features include:
In addition, Google's new support for Java in App Engine is provided with the ability to bring up applications inside the App Engine environment, including:
For more information about the Google Plugin for Eclipse, read the user's guide or the getting started guide. If you just want to install it into Eclipse, you can add the 3.4 (Ganymede) update site (or 3.3 (Europa) update site) into Eclipse's update manager. Those using a 3.5 milestone build of Eclipse are currently out of luck, since Google's feature depends on platform [3.4.0,3.5.0) and thus has a built-in expiration date.
Introducing SQLFire: a memory-optimized, high performance SQL database
The WebSphere Liberty Profile for Developers: An Introduction
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
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