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 Jonathan Allen on Apr 10, 2011
Microsoft Research has begun working on its own graph database, Trinity. Graph databases store data in terms of nodes and edges instead of rows and columns, making them quite effective for loosely and arbitrarily connected data. Potentially uses for this included social networks, movie recommendations, and related product searches.
Trinity is designed as a distributed hypergraph. Unlike a normal graph database that links pairs of nodes, each edge in a hypergraph can connect an arbitrary number of nodes. This can be used to pull together sets of information, such as a user’s profile or the contents of a web page. Both nodes and edges can store heterogeneous data in the form of key/value pairs.
For more information on large scale graph databases in production today look to Facebook’s distributed graph database, has been covered on InfoQ multiple occasions. There are also several commercial and open source projects including GraphDB, InfiniteGraph, HypergraphDB, and Neo4j.
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