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 24, 2009
Microsoft’s service codename “Dallas” is an information marketplace bringing together data, imagery and service providers and their consumers facilitating information exchange through a single point of access.
“Dallas” has been built with and on top of Windows Azure platform, the service consisting of three main components:
Data can be accessed through a REST-based API, but C# proxy classes provide an object model facilitating access from within any .NET program. Services provide their data as ATOM feeds or in a tabular form. Data can be also loaded into Excel through PowerPivot. “Dallas” will soon provide data through SQL Server and SQL Azure queries.
Developers have the possibility to investigate existing content and develop their applications without paying royalties but they need to request an account before being able to start programming.
Microsoft Pinpoint is the materialization of the “Dallas” project. It currently contains data from four countries - India, Netherland, UK, and US –, filed under three main sections – companies, applications, services – each containing several hundred of items. Data is organized in a number of categories - Sales, Security, Computer, Internet, Communication, Financial Management, Training, etc. -, each category being further organized in sub-categories.
Practically, “Dallas” solves a difficult problem: consuming services from different providers, each with his own delivery interface, and helps consumers meet their providers in one place, with one API and one programming model.
More resources: Dallas Introductory Video, Dallas Learning Course, Dallas Team Blog.
Want to know how software releases can be stress-free and happen with one click? Try Go free!
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
The concept sounds quite interesting, a data marketplace where you can buy different data services aggregated under the use of the same API.
Nevertheless I didn't have enough time to look at it ...
Microsoft Pinpoint site went down this morning just when I started browsing it (some 10 hours ago), returning an HTTP 500 error.
It's still in the same situation now, after so many hours !!
Obviously that downtime (if even only on the frontend website) doesn't inspire much trust, especially when we're talking of data services to build apps and infrastructure on...
I wonder if someone has some more details, to be honest in the few minutes I could explore Pinpoint I just saw it as a gallery of Microsoft Certified Partner companies advertising their businesses, no sign of real data (but again, it went down before getting to explore it properly).
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.
1 comment
Watch Thread Reply