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 Peter Cooper on Aug 29, 2006
WebORB is a new Rails plugin by The Midnight Coders that makes implementing services with Ruby on Rails and Adobe Flex (or Flash Remoting) easy. Flex is rapidly becoming a popular option for the front-end for Rails applications in the enterprise with its consistent UI, wide range of dynamic controls, and the widespread acceptance of Macromedia Flash. As opposed to typical HTML and Javascript technologies, Flex UIs work consistently between browsers and are especially useful for intranets or internal applications.
WebORB is a plugin facilitating easy connectivity between existing Rails models and Flex clients and can be installed on both Unix and Windows based operating systems. Flex applications can connect to Rails applications and invoke methods on any Ruby class within the application using the mx:RemoteObject tag. Classes can be registered in an XML file so they can be called via RPC. This makes WebORB a great technology to investigate if you're considering moving an existing application over to using Flex technology on the front-end.
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