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 Feb 25, 2011
Yesterday Josh Odom announced the beta release of Cloud Load Balancers for the Rackspace cloud computing stack. This release comes with their Fanatical Support and a documented API for implementation and management load balancing on their stack, Cloud Servers.
The Details
Each load balancer is assigned a static IP address that can be shared with other load balancers under a single account. For the duration of time a load balancer is active, all IP addresses are persistent and do not change. Supported load balancing algorithms are round robin, weighted round robin, least connections, weighted least connections, and random. Connection throttling is also supported through user defined limits on the number of connections per IP address.
Load Balancers also provides built-in health status checks by routinely inspecting HTTP response codes and if a node experiences failure, the load balancer quickly checks and removes the node from the rotation. Session persistence is maintained via an HTTP cookie and all requests are directed to the same node in a load balancer pool.
Connection logging is Apache-style for HTTP traffic and simple connection/transfer logging for all other traffic. Raw data for debugging and performance tuning are made available via logs which are sorted, aggregated and delivered via Cloud Files.
The Cloud Load Balancers supports multiple protocols:
Support and Documentation
As this is a beta release, it is not yet supported by the Rackspace Cloud Control Panel and only via the programmatic API. However, it does with with full Fanatical Support and the API is available here.
Identity and Access Management for Cloud Apps: A Buyer's Guide
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
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
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
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