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 Dec 03, 2010
Earlier this week Microsoft Research published a paper outlining a framework for Cloud Computing codenamed Orleans. The framework is intended for cloud computing applications where a client such as a PC, smartphone or embedded device is employed. In Orleans, the basic premise is to use concurrency patterns and lightweight transactions on an actor-like model with a declarative specification for persistence, replication and consistency.
a simple programming model built around grains, logical units of computation with private state that communicate exclusively by sending messages ….
The system as a whole can process multiple requests concurrently in distinct grain activations, but these computations are isolated, except at the clearly identified points where grains commit state changes to persistent storage and make them globally visible
Summary of Orleans Definitions:
The Microsoft Research team built Orleans as a cloud computing pattern meant to address the need for scale, multi-tenancy and both reliability and availability. The intention is for the grain model to mimic at a programmatic level the sharded data stores they represent and their inherent capability of flexibility as the application changes over time. Further, to address availability and reliability, the use of grains represented as computations or datums, provides failover capabilities built into the system while preserving consistency and separation of logic.
Orleans has three main components; a programming model or framework outlined in the publication, Orleans: A Framework for Cloud Computing, programming language and tool support and a runtime system. Currently Orleans provides support for C# and they are actively working on F#. The runtime delivers core cloud computing functionality such as persistence, replication, consistency and full life cycle management for versioning, debugging, deployment and monitoring. The team has an informal discussion on Channel 9 which walks through the logical architecture.
This first look at Orlean’s internals is very instructional as to how to architect and build a cloud scale application as the software development world moves from Enterprise computing to Internet scale computing above the transport layer.
Want to know how software releases can be stress-free and happen with one click? Try Go free!
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Automating Error Reporting for .NET Applications
Troubleshoot Java/.NET performance while getting full visibility in production
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
The new idea, though somewhat originated from the melting pot of various invented theories, will take positive effects on new rounds of technology evolution. The work from Microsoft just highlighted the trends of development of computing patterns like Ubiquitous Computing that has been flourishing since last century.
and Promises same as Clojure's promise!
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.
2 comments
Watch Thread Reply