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 Miko Matsumura on Oct 23, 2006
According to the working group: "Web Services Policy defines a flexible policy data model and an extensible grammar for expressing the capabilities, requirements and general characteristics of a Web service, and defines mechanisms for associating policies with Web service constructs."
WS-Policy is a significant standard in the realm of SOA run time governance, and has recieved the attention of many vendor organizations.
The WS-Policy working group recently published a primer which provides an introductory description to this policy language using numerous examples. The WS-Policy Primer 1.5 document lists the following organizations as editors of the working draft: Microsoft Corporation, BEA Systems, Inc., IBM Corporation, Layer 7 Technologies, and webMethods, Inc. The specification has existed since 2002, but was not submitted to the W3C (World Wide Web Consortium) standards organization until recently in spring of 2006.
The submission of the specifications to the W3C have reduced one of the major objections to adoption, and it's likely that more vendors will support WS-Policy going forward. However, one of the issues frequently raised with WS-Policy is that it does not sufficiently articulate policy semantics to the extent needed for many applications of policy in the Web Services realm. While very extensible and flexible, this flexibility does not always produce interoperability between vendor implementations.
The WS-Policy 1.5 Working Drafts can be downloaded 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.
No comments
Watch Thread Reply