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 May 25, 2011
Microsoft has announced Mango, the upcoming version of Windows Phone, a mobile OS that wants to catch up with the competition by providing a plethora of new features: mobile hardware-accelerated IE, multitasking, integrated communication, Silverlight 4 and XNA support, additional sensors, VB.NET support, and others.
Microsoft announced Windows Phone 7.1 (WP), code name “Mango”, during a press conference held in New York and other locations in the world on May 24th. Joe Belfiore, Corporate VP, has presented the three major directions the company wants to pursue with WP:
Microsoft brags about Mango as having 500 new features, a short list of the most important ones including:
Developers can use Windows Phone Developer Tools 7.1 Beta to create applications for WP 7 and Mango, having new profiling tools, location and accelerometer simulation in the emulator, and new templates supporting Silverlight and XNA content in the same application. Visual Basic is a supported language for WP 7.1 development.
One of the problems with Mango is that it does not support Flash, and it is not clear if it will support it in the future. Tim Anderson reported asking a Microsoft representative on Flash support, and got this answer:
“It does not run on the device”, said Watson. Then he added, “It does not run on the device.” Finally, he said, “It does not run on the device.”
Microsoft has partnered so far with Acer, Fujitsu and ZTE to bring new WP phones to the market. Nokia remains the main WP manufacturer, but there is nothing known about their current developments, only that they plan to have one this year. Mango will be made available to all WP 7 customers for free in Autumn.
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Automating Error Reporting for .NET Applications
RDBMS to NoSQL: Managing the Transition
Troubleshoot Java/.NET performance while getting full visibility in production
The WebSphere Liberty Profile for Developers: An Introduction
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.
3 comments
Watch Thread Reply