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 Nov 14, 2006
Last week Mono hit its 1.2 release. Novell uses Mono in server form for both ZenWorks and iFolder in its Suse Linux Enterprise 10 platform. This release was primarily focused on performance and scalability improvements. Enhancements can be found across the board in support for Windows Forms and System.Drawing, .NET 2.0 parity in C#, and debugger support for both X86 and X64.
InfoQ spoke to Miguel to find out more about the release. On what's new in 1.2, Miguel explained:With this release, we've solved an important issue by making it easier to translate the Microsoft user interfaces to Linux, an important contribution in increasing the number of client-side Linux applications,” said Miguel de Icaza, vice president of developer platforms at Novell and maintainer of the Mono project. “Now feature complete, Mono has matured to the point that we believe the migration from ASP.NET and Windows Forms to Linux is easier than ever before and gives developers access to all the added benefits of Linux.
Windows.Forms 1.2, complete System.Drawing, much higher performance, ports to many new architectures, generics, C# 2.0 and preview for a lot of the 2.0 APIs. Full details are here: http://www.go-mono.com/archive/1.2/
On interesting uses of mono around the net:
Unity (www.unity3d.com), wiki.com (the engine behind the DekiWiki in Wiki.Com), http://www.govtrack.us/ (tracking the US congress) and of course our own applications Beagle (http://beagle-project.org/Main_Page), F-Spot (f-spot.org) and Banshee
(http://banshee-project.org/Discover/Home)
Asked about the impact of the Novell-MS announcement, Miguel answered that it's too soon to tell (it just happened last week), but "at least a big part of our agreement (Office XML support) is being done with Mono."
Development is now shifting towards Mono 2.0, code name “Sirloin”. The planned featureset inclues:Mono 2.0: Core
Gtk#
Languages:
Thanks Miguel and congratulations to the entire Mono team on a succesful release!
Introducing SQLFire: a memory-optimized, high performance SQL database
Automating Error Reporting for .NET Applications
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
RDBMS to NoSQL: Managing the Transition
Branching & Merging Efficiently: A Guide to Using Process-Based Promotional Patterns
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
Two sides to the coin:
- With Java GPL'd, maybe Mono finally gets a decent VM
- With Java GPL'd, there is no reason to keep Mono
Peace,
Cameron Purdy
Tangosol Coherence: Distributed Caching for Java and .NET
I'd have to disagree with Cameron - there are lots of GPL Languages already , and nobody ever suggested that GNU version of C or C++ was going to disappear when Mono appeared under the GPL.
As a Java Developer , I'm looking forward to some of the 'Mashups' that will now (technically and Legally) be possible between the languages. Top of my wishlist would be a version of C# that runs within the JVM (a bit like JRuby does). C# and Java are already syntactically close, and that would reduce the cost of switching back and forward even further.
Paul, Technology in Plain English
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