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 James Vastbinder on Dec 01, 2010
Last week Microsoft launched HTML5 Labs where they intend to post early prototypes of applications running on unstable web standard specifications for .NET developers. The intent is to create an early dialogue with the developer communities and higher fidelity implementations of draft specifications. The first two prototypes made available are IndexDB, an application based on the draft web specification for the storage of large amounts of structured data in the browser and an example WebSocket implementation.
Microsoft Implementation
The download from Microsoft contains a .NET implementation including:
WebSocket Draft
WebSocket is a draft protocol intending to define a bi-directional full-duplex communication protocol to allow web browsers and web servers to communicate without the HTTP protocol overhead. It is designed to be implemented in both web browsers and web servers. The communication begins once an initial connection has been established between browser and server. If adopted, WebSocket will deprecate the HTTP long-polling mechanisms in use by developers today. The WebSocket API is under the jurisdiction of the W3C Web Application Working Group while the IETF owns the working specification.
Currently the WebSocket draft is implemented in FireFox 4, Chrome, Opera 11, Safari 5 and both IE 8 & IE 9. Apple has even implemented WebSocket in the latest release of iOS 4.2, while developers must wait for support in Windows Phone 7 and Android.
WebSocket Setbacks
Earlier this month, preliminary WebSocket implementations in FireFox 4 and Opera where disabled due to security concerns. The problem lies not with web browsers, nor truly WebSocket, but with poorly implemented caching proxies which sit on most corporate and enterprise firewalls. Within FireFox, it is possible to re-enable WebSocket by browsing to about:config and toggling network.websocket.override-security-block. General consensus is that eventual adoption of WebSocket in inevitable yet in an altered form to alleviate the current security concerns, but some feel XMPP sufficiently solves the same problem space.
Automating Error Reporting for .NET Applications
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Troubleshoot Java/.NET performance while getting full visibility in production
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
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
> Currently the WebSocket draft is implemented in FireFox 4, Chrome, Opera 11, Safari 5 and both IE 8 & IE 9.
I'm not sure about WebSockets being supported/implemented in both IE 8 and IE 9. According to these[1] two[2] sources they aren't.
[1]: html5test.com/
[2]: caniuse.com/#feat=websockets
Tomas,
You are correct, IE8 and IE9 are relying on a Silverlight client to provide a WebSocket client in the browser. It is not built into the browser itself.
-James
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.
2 comments
Watch Thread Reply