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 Feb 09, 2011
Microsoft has created a JavaScript library enabling developers to consume OData from within the browser.
The Open Data Protocol (OData) is a protocol created by Microsoft enabling the consumption of data in a RESTful way based on HTTP, AtomPub and JSON. datajs is an open source cross-browser JavaScript library, also released by Microsoft, easing the task of developers to access OData from within the browser. datajs will be enhanced in the future to access HTML5 functionality exposed by browsers.
The datajs API currently contains two main functions:
OData.read = function (url | request, [success(data, response)], [error(error)], [handler], [httpClient], [metadata])
OData.read is used to retrieve data from an OData-enabled service as an AtomPub feed or a JSON document. The library uses a RESTful convention, accessing each resource through an URI. The developer may specify a handler for errors, and another for content received from the service.
OData.request = function (request, [success(data, response)], [error(error)], [handler], [httpClient], [metadata])
OData.request is used to add new data, to update or to delete existing data. Besides functionality similar to OData.read, OData.request can be used to send data in batches.
datajs uses XMLHttpRequest to make network calls by default, but a different HTTP client can be used.
Microsoft plans to enhance datajs to access HTML5 functionality in the future such as the local storage provided by IndexedDB.
OData is offered by Microsoft under the Microsoft Open Specification Promise (OSP), and currently implemented by Microsoft across a number of Azure services, by Netflix, Facebook, ebay and others. datajs is offered under the MIT License (MIT).
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