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 James Vastbinder on Jan 25, 2011
Last week Amazon announced Elastic Beanstalk, but there is also an Open Source project named SteamCannon. SteamCannon is sponsored by RedHat and has been in active development since September 2010. Written in Ruby and running on top of TorqueBox, SteamCannon is a solution to simplify the deployment of Java EE and Rails applications to EC2 and VirtualBox. There are many other differences, as outlined by Ben Browning in a news post late last week.
The Differences
Amazon has announced with subsequent releases they will support additional languages yet SteamCloud supports both Java and Ruby today. In regards to deployment packaging, SteamCloud supports .war, .ear, .rails, .rack and more. Essentially if you can deploy it in TorqueBox and JBoss AS6 it is supported.
As to the application environment, SteamCannon has better multi-tenant support in that it allows multiple applications to be deployed in a single environment using different context paths whereas Beanstalk creates a new environment per application. Using JBoss AS6 allows SteamCannon to support several logical architectures from a developer configuration with PostgresSQL to a three tier configuration with mod_cluster, JBoss AS6 and PostgreSQL. SteamCannon also supports clusters and provides load balancing via a mod_cluster instance enabling session replication and caching within the cluster.
Coming Features in SteamCannon
New Release Soon
There is a new release of SteamCannon coming in the next few weeks, version 0.3 expected to launch on February 1, 2011. Version 0.3 will add support for handling multiple cloud credentials, a client API, support for all EC2 regions, and most notably support for running inside VirtualBox on a single machine thus supporting private cloud capabilities.
Tutorial: Integrating SQLFire with tc Server and Spring Data
Troubleshoot Java/.NET performance while getting full visibility in production
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
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
This isn't a comparison its a sales pitch for SteamCannon.
Seriously if something is going to be a comparison then it should be that rather than statements like "better monitoring support and metrics" without actually having any proof. Finishing off with mentioning its only at version 0.3 while the Amazon service is a fully supported commercial solution.
Whether SteamCannon is better than Elastic Beanstalk is something I'd like to read about but that does mean actually comparing pieces rather than just making statements.
Agreed!
I look forward to having more option than App Engine and Beanstalk but this is no comparaison.
The linked article is worth reading - it is much more of a comparison than the summary here.
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.
3 comments
Watch Thread Reply