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 Michael Stal on Sep 16, 2011
At the GridWeek 2011 Conference the Software Engineering Institute (SEI) at the Carnegie-Mellon-University has released an update 1.2 of its Smart Grid Maturity Model (SGMM). According to its definition, SGMM is
a management tool that utilities can leverage to plan their smart grid journeys, prioritize their options, and measure their progress as they move toward the realization of a smart grid.
According to Wikipedia, a
Smart grid is a type of electrical grid which attempts to predict and intelligently respond to the behavior and actions of all electric power users connected to it - suppliers, consumers and those that do both – in order to efficiently deliver reliable, economic, and sustainable electricity services.
In contrast to current centralized grids, smart grids integrate consumers and suppliers in a decentralized network. The “smart” in smart grid refers to the combination of electric power grids with IT. This combination of infrastructures is supposed to address challenges which conventional grids cannot handle such as the problem of coping with a variety of large and small energy consumers and suppliers in a reliable and secure way. In the upcoming years, today’s grids need to be be transformed into smart grids.
The SGMM is SEI’s approach to support utilities this transformation.
In the update the SGMM Compass Survey will help collect new data
According to the SEI Web site SEI-Certified Smart Grid Maturity Model (SGMM) Navigators
are industry experts who have been trained and certified to guide utilities through the SGMM Navigation process. The SGMM Navigator works with the utility’s smart grid team to complete the SGMM Compass assessment on a consensus basis – promoting valuable internal discussion of current status and shared objectives. After scoring and analyzing the survey, the Navigator leads a second workshop to review the survey results and use them to set consensus aspirations for an agreed planning horizon -- and to discuss related motivations, obstacles and required actions.
If you are interested in more details, you may read introducing articles or visit CMU SEI’s Smart Grid site.
Requirements, quality and test management e-Kit
The WebSphere Liberty Profile for Developers: An Introduction
Introduction to WebSphere Liberty Profile
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.
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