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 Jul 18, 2011
Mono is back where it started. Miguel de Icaza and his developers have all legal rights to continue developing Mono and all related products due to an agreement with SUSE, now part of The Attachmate Group.
The reason why Xamarin, the company that has continued developing Mono after Novell was bought by The Attachmate Group, announced their interest in hiring consultants a week ago became clear today when SUSE, a former division of Novell, and Xamarin announced an agreement granting Xamarin a “broad, perpetual license to all intellectual property covering Mono, MonoTouch, Mono for Android and Mono Tools for Visual Studio.” In exchange, Xamarin will “provide technical support to SUSE customers using Mono-based products.” One important aspect of the agreement is that Xamarin is given “stewardship of the Mono open source community project.”
Both parties have something to gain from this agreement: SUSE will fulfill their support obligations towards present and future customers using Mono products, while Xamarin gets all the IP rights needed to develop Mono and related tools without worrying for a legal suit.
Miguel de Icaza has announced the Xamarin Store from where developers can buy MonoTouch for iOS and Mono for Android. Also, Xamarin will take over “MonoDevelop and the other Mono-centric in the Mono Organization at GitHub.” A new roadmap is drawn for MonoTouch and the Mono for Android. On the immediate term, priority are major bugs/issues reported by customers, while for short term Xamarin intends to incorporate some of the code developed for the last 2-3 months back into MonoTouch and Mono for Android. Jerry Stedfast, a Mono developer, added that they already started merging with the original code:
We've switched to using the original MonoTouch and Mono-for-Android sources, but we'll be merging some of the things we did better in xtouch/xandroid into MonoTouch and Mono-for-Android respectively (for MonoTouch 5.0 and Mono-for-Android 2.0).
On medium and long term, Xamarin plans among others iOS 5 support, asynchronous programming with C#, Mono GC for iPhone, C++ interoperability, and cross platform API for unified code across all major mobile OSes: iOS, Android and WP 7.
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
Building HTML5 Apps in Hours, Not Days
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
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