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 Steven Haines on Jul 17, 2008
"The Eclipse Foundation is making use of the UDC to gather information about how the community is making use of Eclipse technology. The Foundation's immediate interest is to provide feedback to the project teams about the use of their technology in the field. The UDC is currently implemented with this purpose in mind (i.e. the exemplary application of the UDC technology is concerned with providing data to the Foundation)."
The UDC collects information about bundle events, workspace events, and commands using "monitors". A monitor is a Java class that installs a listener to capture events that should be of interest to the Eclipse development community. The UDC could be considered an automated market research tool with a potentially large reach (it is packaged with every Ganymede installation.) And of course Eclipse does not force this feature on its users, Ganymede prompts the user before sending any information back to the Eclipse Foundation. For those concerned with privacy, the UDC does not capture any personal information, including IP Address. In an article in JavaLobby, Mike Milinkovich, Eclipse's executive director, wrote:
"As you can imagine with any data collection technology, privacy is a huge concern. Therefore, to be clear, UDC is 1) opt-in, so only people that agree to send the data will participate, and 2) completely anonymous. No personal data, including IP addresses, is being collected."
It has "potentially" large reach because if enough Eclipse users opt-out of submitting UDC bundles then the Eclipse Foundation will not receive enough representative information to be able to improve Eclipse to meet its developers' needs. In a response to the JavaLobby article, Zviki Cohen raised a good point, that "collecting usage data is a "missing link" for desktop apps. It one of the key shortcomings when compared to web apps." Web applications are already monitoring user activities, so UDC attempts to bring this same paradigm to a desktop application.
Beyond providing insight into Eclipse usage, in an article in The Register, Milinkovich stated that the UDC will help quantify Eclipse usage which he hopes will provide Eclipse with hard ammunition to use against Sun Microsystems' NetBeans.
Tutorial: Integrating SQLFire with tc Server and Spring Data
Early Access! Download JBoss Developer Studio 5.0 now, with packages for Mac, Windows or Linux!
RDBMS to NoSQL: Managing the Transition
Branching & Merging Efficiently: A Guide to Using Process-Based Promotional Patterns
Introducing SQLFire: a memory-optimized, high performance SQL database
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
For me the UDC is fine when I have the possibility to use it or not. But I can’t switch it completely off! Yes I can choose to send the data. But I would like to switch it off because eclipse is already heavy enough and UDC will make my eclipse even more slow.
If you opt to turn off the UDC in either the wizard or in the preferences, it stops monitoring and doesn't start up its service. The plug-in still starts because it has to check to see if it should start up the various services and hook up those monitors. If you're seeing different behaviour, you should create a bug report.
Thanx!
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