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 Michael Stal on Oct 14, 2011
On 12th October IBM has unveiled in New York what the IT company claims to be
the industry’s most advanced cloud services and software designed from the ground up for enterprise clients.
It is the goal to support 200 million users by the end of 2012 due to the migration of client applications and processes to the new cloud service platform. In particular, this might be an additional option for software development organizations interested in building their own cloud or leveraging the SmartCloud infrastructure hosted by IBM.
An advantage of a Platform-as-a-Service for developers and architects is the ability to directly develop applications for the cloud. Thus, they can focus on the application, instead of dealing with complex infrastructure issues. Competitors in this area include Microsoft’s Windows Azure and the Google App Engine. It is a matter of trust to deploy secure information or services on a Cloud operated by another company. Thus, buying IT infrastructures from IBM to create clouds might be a viable alternative. In addition, IBM is considered by many corporations as an IT vendor with a long experience in mission-critical development of medium- to large-scale solutions.
According to IBM,
the Application Services will run on IBM’s SmartCloud Enterprise and Enterprise+ - specifically designed to run enterprise workloads, at committed business centric service level agreements.
In detail, the whole IBM Cloud portfolio comprises the following constituents:
The company also announced a new partnership with the Cloud-storage company Nirvanix. According to the press release
Under the terms of the OEM agreement between IBM and Nirvanix, IBM will include cloud storage technology from Nirvanix designed to enable customers to upload a file of any size from anywhere in the world and access it anywhere—as opposed to forcing customers to upload the same file multiple times in multiple geographic regions and imposing strict file size limitations.
The new services will be available as beta in this quarter, providing Java support and cross-platform support. The IBM public Cloud infrastructure as well as a migration services will be first available in the US in 2012.
More information for interested readers is available on IBM’s web site.
Introducing SQLFire: a memory-optimized, high performance SQL database
The WebSphere Liberty Profile for Developers: An Introduction
Early Access! Download JBoss Developer Studio 5.0 now, with packages for Mac, Windows or Linux!
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