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 Aug 23, 2011
Xamarin's first official Mono release came out earlier this month with many bug fixes, OS X Lion support, a “vastly improved WCF stack”, and better debugging support. The version number is 2.10.3, which makes it a short-term support release. Those who desire a long term commitment to support should stay with the 2.6 series until Mono 3 is ready.
The bug fixes cover a wide gambit including the C# compiler, the JIT compiler, WCF, ASP.NET, OS X, and ADO.NET. The full list is available in the release notes. While there were also new features in most of these categories, by far the biggest winner is WCF with the following features:
It should be noted that Mono still supports only a very small subset of the WCF stack. Xamarin's current plan is only to support those features that are also available in the Silverlight runtime. The size of the full WCF stack makes implementing it completely untenable without corporate support. Another possibility, though unlikely, is that Microsoft open sources the WCF stack in the same fashion that they open sourced the ASP.NET MVC stack.
Speaking of ASP.NET, below are some of the features that made it into this release. It should be noted that support for Web Forms has always been on shaky ground, both legally and from a long-term commitment, and those wishing to use Linux as a web server should strongly consider focusing on ASP.NET MVC.
A lot of changes have been made to help with debugging too.
In related news, Mono’s C# 5 compiler is currently on par with the last public release from Microsoft. Both companies are having trouble with some of the more complex scenarios dealing with expressions and their respective teams are in contact with each other. More information is available in the Q&A session recorded at Monospace.
Automating Error Reporting for .NET Applications
RDBMS to NoSQL: Managing the Transition
Troubleshoot Java/.NET performance while getting full visibility in production
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
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