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 Nov 17, 2011
Google have announced that their Google Plugin for Eclipse is now open source. Originally made available in April 2009 as a closed-source product, following their purchase of the Instantiations tooling arm in September 2010 the WindowBuilder and CodePro profiler was donated to the Eclipse Foundation in December 2010. Until yesterday, the GWT Designer project was still closed source; now it, along with the Google Plugin for Eclipse project are available under the Eclipse Public License at Google Code.
The basis of GWT Designer remains the WindowBuilder project at Eclipse.org; the two will continue to evolve where they are and have releases as scheduled by the appropriate organisations. However, fixes and issues for GWT Designer can now be provided by the community at large rather than solely by Google employees.
Red Hat's Max Andersen thinks this is good for the developer experience:
We have many developers using Google's Eclipse plugin to develop GWT-based applications targeting the JBoss Application Server. We are especially interested in seeing the Google Eclipse plugins being able to target multiple runtimes such as the JBoss Enterprise Application Platform and Google App Engine in a uniform way.
In the end this should allow for much more stable and uniform user experience. This goes not only for JBoss Tools plugins integration, but for integration across the Eclipse ecosystem such as Eclipse Web Tools Project and m2eclipse.
Reactions to the news on the GWT mailing list by Eric Clayberg of Google have been uniformly positive. Eric was formerly project manager of the WindowBuilder projects at Instantiations, and now also project lead of the Eclipse WindowBuilder project, having been involved with the tool for the past seven years.
Although the GWT code isn't being donated to Eclipse.org, the underlying tool suite based on WindowBuilder can now create Swing, SWT, XWT, RCP and now GWT can be developed in a familiar and common environment between them all. This wraps up the tool software acquired by Google in August last year, valued at the time at $5 million.
Tutorial: Integrating SQLFire with tc Server and Spring Data
RDBMS to NoSQL: Managing the Transition
Banking Case Study: Scaling with Low Latency using NewSQL
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
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.
1 comment
Watch Thread Reply