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 Jul 02, 2011
In an article for HowStuffWorks Jonathan Strickland addresses his perspective on Web 3.0. He believes in Web 3.0 as a disruptive new technology. Other experts have different opinions what the Web 3.0 is or what it should be. Some think, it might only comprise an evolutionary step, leveraging semantic metainformation. So is it coming and what exactly is the Web 3.0?
Since the increasing penetration of applications like Facebook, Twitter, Flickr as well as new user-based media like blogs or podcasts, the so-called Web 2.0 has become state of the art. However, Web 2.0 is rapidly reaching its limitations in terms of user experience and personalized content. Web 3.0 presumably will be the next step of the Internet evolution. There is a lot of discussion whether Web 3.0 will be just an realization of Tim Berners-Lee’s idea of a Semantic Web. Although most experts have different anticipations regarding the new Web, at least most of them seem to agree on the traits of Web 3.0:
For example, Knowledge@Wharton reports from a panel with Travis Katz, Mitch Kapor, Shannon Berning, and Bryan Sabrian. The panelists agreed that there were too much information in the Web today so that ways are required for filtering out the relevant information. These filtering and search mechanisms, however, need to take the personal profile of the user into account. In addition, the Web could turn into a People Web where the information will more emphasize people and their interactions instead on focusing on the system or infrastructure. ´
In his blog posting called Say Hello to Web 3.0 the author Waqas E. considers seven technologies to be particularly essential for the new incarnation of the Web. The author is not a professional engineer, but reveals some expectations from the user's perspective:
For architects and developers, such a Web 3.0 would definitely have a lot of consequences with respect to application development, if they need to leverage all the aforementioned technologies. Probably, mash-ups and APIs will gain importance.
Although some of the experts statements are very concrete, we should not forget that it is very difficult to anticipate the future. Technologies and concepts in the Web tend to be fast moving targets.The Semantic Web is not developed as experts thought a few years ago. Opinions on the concrete shape and function still vary a lot as described in Wikipedia.
For interested readers, there is an interesting video that reveals some aspects of Web 3.0. So, what do you think, should be part of an upcoming Web 3.0?
Requirements, quality and test management e-Kit
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
The WebSphere Liberty Profile for Developers: An Introduction
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!
I proposed my own vision on the future development of Web in:
on-meaning.blogspot.com/2011/06/great-blunders-...
Briefly said, we should have semantic ecosystem, which will change not only Web itself, but also the way we interact with computers. What Semantic Web lacks is human-friendliness, simple and affordable approach to integrate semantics. And this proposal tries to fill this gap.
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.
1 comment
Watch Thread Reply