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 Mar 29, 2010
It seems like every year we relay the announcement that the .NET platform is going to be available on the Nokia S60. In 2007 the now defunct Red Five Labs was talking about Net60, a version of the .NET Compact Framework. Then in 2008 Nokia announced that Silverlight 2 would be demonstrated at the MIX08 conference. It has been two full years since then and we are just now seeing a public Silverlight for Symbian beta.
While the rest of the world is gearing up for Silverlight 4, developers targeting the S60 platform are limited to Silverlight 2. This means going back to Expression Blend 2 and sticking with Visual Studio 2008.
And even in the context of Silverlight 2, the platform is severely limited. Looking at the list of unsupported features, this appears to be more of a tech preview than an actual beta release.
- Cryptography
- Deep Zoom
- DLR
- Digital Rights Management (DRM)
- Expression trees
- HTML DOM bridge
- JavaScript programmability
- LINQ to SQL
- Localization of Silverlight resources
- Reflection
- Sockets
- Visual Basic
- Windows Communication Foundation (WCF)
And these are just the completely unsupported features. There are many common scenarios that lead to undefined behavior or outright browser crashes including having multiple plug-ins on the same page. One can’t even use a single Silverlight plug-in until 200 milliseconds after the onLoad event fires.
Between Silverlight and the S60 operating system is the .NET Compact Framework. Unfortunately developers will not be able to use it; the framework is restricted specifically to running Silverlight plug-ins. And unlike Windows Phone 7, there will be no support for S60-specific features or XNA-based games.
Introducing SQLFire: a memory-optimized, high performance SQL database
Automating Error Reporting for .NET Applications
Troubleshoot Java/.NET performance while getting full visibility in production
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Big Data, Cloud & Mobile: Navigate the New Development Reality with Resources from IBM
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