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 Johan Strandler on Jul 30, 2007
Since the acquisition of Logicblaze in april, things have been quiet with regards to what shold happen with the Logicblaze open source SOA product FUSE. Last week however, IONA presented their open source strategy roadmap by announcing a merger of the former Logicblaze FUSE product and IONAs own Celtix product. The new open source product line will keep the FUSE brand and will consist of four product modules that can either be deployed together or independently:
The merger of the products has lead to some exclusion from both of the earlier products. From the Celtix product an AMQP implementation based on the Apache Qpid project has been removed. From the Logicblaze FUSE, a BPEL engine based on the Apache ODE project, an UDDI registry, the Jetty Web server and the Liferay portal has been removed.
Commenting in the FAQ on the removal of the AMQP and Qpid implementation, IONA "...choose to postpone their commitment for commercial support until they gain greater maturity and market traction". As for the removal of the BPEL engine in their new open source product line, IONA says that they "...encourages the use of any JBI-compliant BPEL engine with the FUSE ESB". For those that "...aren't happy with the open source options, IONA does provide the Artix Orchestration product".
Given the announcement, it seems that IONA has chosen a business model for open source similar to the one IBM uses for it's WebSphere product line, which includes one proprietary product line plus a complementary open source alternative through the WebSphere Application Server Community Edition. IONA now pushes the Atrix proprietary product line and the open source alternative FUSE.
From this announcement we see that the Java Business Integration (JBI) path started early on by Logicblaze has a firm continuation within IONA. The FUSE ESB should be able to function as the JBI based glue between FUSE products as well as to other products. Another interesting point is the inclusion of of the new Apache Camel project used in the FUSE Mediation Router product. Apache Camel is a rule based routing and mediation engine which provides a POJO based implementation of the Enterprise Integration Patterns.
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