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 Dec 19, 2006
Seeing parallels between the computer industry of 30 years ago and the robotics industry of today, Microsoft is determined to not be left out of the next big thing. For their initial play, Microsoft has released the Microsoft Robotics Studio.
The robots industry, much like the computer industry of yesteryear, is a fragmented mess. There are countless hardware platforms, processors, and operating systems. Moving from one robot to the next can involve extensive retraining on the language and API de jour.
Just like in the PC market, this situation cannot last forever. As the demand for robotics increase, market pressures to reduce costs will result in the need for de facto standards. Following the original DOS game plan, Microsoft wants to set those standards by providing the software platform that abstracts away the differences between the different hardware systems.
According to a Microsoft Press Pass interview,
The Japanese Robot Association predicts that by 2025, the personal robot industry will be worth more than $50 billion a year worldwide.
With potential like that, it is no wonder Microsoft wants in on the ground floor. And in order to gain the widest possible audience, Microsoft is bringing managed code to the world of robotics.
In the past, languages with very small memory footprints like C or even assembly were used to program robots. As memory sizes increase, the use of managed code such as C# or VB becomes far more feasible. Even dynamic languages such as IronPython can be used.
Microsoft Robotics Studio is free to download for hobbyists and students. Commercial developers will need to purchase a license, which currently runs for $399.
Automating Error Reporting for .NET Applications
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
RDBMS to NoSQL: Managing the Transition
Troubleshoot Java/.NET performance while getting full visibility in production
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