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 Jun 07, 2007
Microsoft has been pushing a lot of new technology lately, but is any of it actually useful? In the case of .NET Micro, Leviton Manufacturing says it is, though the far more interesting technology is Z-Wave.
In Embedded Enterprise Magazine, Leviton Manufacturing talks about how they used the new Z-Wave protocol and .NET Micro to quickly design a new generation of their home automation products.
Z-Wave is a narrow band radio frequency protocol used for wireless devices. There are currently over one hundred companies pledged to supporting it in home automation products. One of its most important features is that it does not have a master node. Each node can automatically route messages from other nodes, greatly increasing the communication range beyond that of any single device.
.NET Micro's place in this story is rather boring. As per Microsoft's master plan, C# and .NET Micro were chosen by Leviton Manufacturing as the de facto platform for implementing their new Z-Wave devices. What follows reads like a MS press release.
Speed is a central theme of the Vizia RF Foyer story. “We’ve shown that you can reduce the time it takes to get your product to market with the .NET Micro Framework,” says Leier. “That really changes the game for embedded device designers and developers. Now they can very quickly and very easily add wired and wireless networking to their products.”
“We want to go to the mass market,” says Hendler, “so the .NET Micro Framework was the most cost-effective platform for us to adopt. It also delivers the ability to innovate on and is easy to find developers to program on – and our customers are already comfortable working in the .NET world. The price point is excellent and the value proposition in terms of features and flexibility is great. And based on our testing, it’s very reliable.”
Despite the market-speak, there is some real potential here. The embedded device market now has an army of Microsoft-trained developers waiting at the gates, every one of them eager to use their hard-won .NET skills on something other than building web sites.
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
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
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