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 Abel Avram on Dec 08, 2009
Vedea, or Microsoft Visualization Language from Microsoft Research Computational Science Laboratory, is a new language for creating interactive data-driven visualizations.
The language is built on .NET 4.0’s DLR with a syntax similar to C#’s with some differences:
A binding is an assignment connecting one field to another, like in this example:
textbox.Text := slider.Value;
This means that when Value changes, Text will also change accordingly. A bi-directional binding looks a bit different:
textbox.Text :=: slider.Value;
That means that Text changes when Value changes, but also Value changes when Text does. Binding has interesting applicability especially when LINQ expressions are involved. Visual items – mouse position, clicks, drag, slider position, etc. – can be related to complex data that can be used through a sequence of operations. The user can work with data through simple keyboard, mouse or touchscreen actions, but also changes in the data can easily be reflected through visual changes on the screen. While such operations can be done with any language, Vedea has the merit of making it simpler.
A top syntactic construct is ScDS which relies on a host of providers – netCDF, HDF, SQL, CSV, etc. - to get complex data from various sources. The interesting bit is that such data “supports named variables, meta-data on variables (units of measure, dimensionality and other annotations) and the use of variables to form coordinate systems onto other variables.”
Vedea will come with new graphical ways of displaying data going well beyond pie charts that have been used for the last decades. Among the features are:
- Hierarchical scenegraph
- A full set of 2d primitives (polygons, lines, ellipses, circles, curves, arcs, images, text, etc)
- A full set of 3d primitives (cubes, spheres, capsules, cylinders, pipes, images, text, meshes, textures, materials, height-maps, cameras and lighting)
- Solid and alpha-blended (semi-transparent) colors
- Map object (using data from Bing Maps/Virtual Earth) which can be combined with 2d and 3d primitives
- A rich library of rendering utilities (e.g., Perlin noise, warping functions, color management)
- Animation features (linear and exponential interpolation for smooth variation of any Vedea variable or visual property)
- Direct binding of data to visuals (e.g., create one circle for every row in a database; bind properties of the circles to columns in the database)
- Planned support for Network viewers, volumetric renderers, physics effects and other high-level graphics constructs
Vedea will be made available in early 2010.
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Automating Error Reporting for .NET Applications
How ALM Supports Business Processes
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