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 Dec 23, 2009
Moonlight 2.0 (final version) comes with a promise from Microsoft to help the developing of Moonlight 3 and 4, and a new MS Covenant to end users protecting them from patent infringement by using Moonlight.
Moonlight 2.0 Beta 1 was announced in August 2009. The beta phase ended, and the final Moonlight 2.0 is available for download. It runs in Firefox/Linux on Mono 2.6, Cairo and Gtk+. The team is working on running it also on Chrome/Linux. Moonlight 2 currently consists of “142,000 lines of C/C++ code and 320,000 lines of C# code (125,000 lines of code came from Microsoft's open source Silverlight Controls)”, according to Miguel de Icaza.
Microsoft has extended their promised collaboration with Novell to further help developing Moonlight by providing the Silverlight 3 & 4 test suites. Moonlight 3 Beta will be available in the first quarter of 2010 and the final version during the fall of 2010. Moonlight 4 will follow shortly after that.
Microsoft made an important and necessary step by extending the Patent Covenant to End Users of Moonlight. This covenant protects not only users using Moonlight from Novell, but users getting Moonlight from any Linux distributor and running it on any Linux flavor. This actually means that Moonlight can be included in commercial Linux distributions. One caveat: Microsoft Media Pack, containing the MP3, VC1, H.264 and AAC codecs, were licensed only to Novell because they were bought by Microsoft from the original owners and the right to use them could not be extended to everyone unless a hefty price was paid. Third party Linux distributors can use open source codecs (Ogg, Vorbis, Theora), can purchase a license from MPEG owners, sub-license from Microsoft, or simply write their own codecs.
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.
Great, so Microsoft has offered up yet another Covenant.
Google "Covenant".
No matter how you to try to spin it, a Covenant is a
promise, with strings attached.
So, what does Microsoft expect in return? Never mind that
Microsoft reserves the right to modify and even discontinue
the "covenant".
Wow, what a nice choice of words to put you at ease, yet still
give them the power to pull the rug out.
Forget "covenant". I would want a legal "license".
Sorry, it's just me.
Great,
Forget "covenant". I would want a legal "license".
Sorry, it's just me.
How the hell is Microsoft suppose to give a license when it's Novell that is developing Moonlight?
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