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 Charles Humble on Feb 23, 2011
The Apache Software foundation has announced that Apache Chemistry has graduated to become a top-level project.
Apache Chemistry is an Open Source implementation of the OASIS CMIS (Content Management Interoperability Services) standard. Originally created by EMC Corporation, IBM and Microsoft, the CMIS specification became an OASIS specification on May 1, 2010. Many of the Apache Chemistry code committers are also members of the OASIS CMIS Technical Committee.
CMIS provides an interface for an application to access a content management repository. To do so it defines a core data model which describes the persistent information entities that are managed by the repository, along with a set of Web Services and RESTful AtomPub bindings that can be used by the application to work with one or more repositories/systems.
A number of vendors now provide content management and portal products with CMIS-compliant repositories. These include Alfresco, EMC Documentum, IBM FileNet, Microsoft SharePoint, Nuxeo, and OpenText Enterprise Library Services.
As well as providing an interoperable API to CMIS repositories, Apache Chemistry also offers libraries to build CMIS-compliant repository connectors. It is widely used in enterprise content management solutions. The main Java-based OpenCMIS Chemistry sub-project is deployed in both Open Source and commercial products and solutions by Adobe, Alfresco, Metaversant, Nuxeo, OpenText, OpenWGA, and SAP, among others.
In addition to the Java sub-project Apache Chemistry is working to support other languages including PHP, Python and the .NET family of languages, with the Python version currently the most advanced. Florent Guillaume, Head of R&D at Nuxeo said
We have supported Chemistry from the start, and we are so confident in the technology that we have included it as a core connector for the Nuxeo Enterprise Platform. Through Chemistry, many software platforms, such as Java, Python, PHP, and .NET, will be able to adopt the CMIS specification, which benefits both servers storing content documents or other assets, and the applications interacting with them.
As with all Apache projects, the code is licensed under the Apache Software License v2.0.
Introducing SQLFire: a memory-optimized, high performance SQL database
Early Access! Download JBoss Developer Studio 5.0 now, with packages for Mac, Windows or Linux!
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
CMIS is a great inititive, but the writer needs to get his facts right. AIIM did not originally create CMIS. Give credit where it is due, because CMIS was originally created by IBM, who with Microsoft presented it to OASIS. AIIM suports standards but does not not create any in this area itself: it sometimes coordinates and promotes them.
Rory,
You are quite right, thanks for pointing this out. I've amended the text to include accordingly also including EMC since they were are also involved.
Charles
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