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 Feb 17, 2012
In response to demands for simpler data access, MongoDB is introducing the Aggregation Framework. This library uses a declarative pipe-line notation to support features such as SQL-like group by operations without having to write custom JavaScript routines.
After the “aggregate” clause, most pipeline operations begin with a “$match” clause. Together these act like SQL’s from and where clauses or MongoDB’s find function. Up next is the “$project” clause, which again looks a lot like its SQL or MongoDB counterpart (though unlike SQL it is properly located at the end of the expression).
The next operation is rather unique to MongoDB’s Aggregation Framework. Unlike most relational databases, MongoDB can natively store arrays within a row/document. While convenient for all-or-nothing access, this can make writing reports that need to use a combination of projections, grouping, and filtering quite complicated. The “$unwind” clause breaks down the array into single elements, which are then returned along with the rest of the document.
The “$group” operation serves the same purpose as SQL’s Group By clause, but works more like the LINQ grouping operators. Instead of getting back a flat row, the result set continues to be a nested structure. This allows it to return aggregate information such as counts and averages along with the actual documents, in whole or in part, that make up each grouping.
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