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 Alex Blewitt on Jun 08, 2011
Oracle has announced that the JavaSE 7 governing JSR (336) has passed the public review ballot. Google voted against the vote, Werner Keil abstained, and no vote was received from Credit Suisse. Many others adding their concerns regarding the ongoing licensing dispute between Sun/Oracle and Apache.
Java releases are referenced with a JSR which lists the contents of each release, by reference to other JSRs. These have often been completed ahead of the JSR vote (though some, like Project Coin, are effectively ongoing through into Java 8) so the act of JavaSE JSR approval is really a rubber-stamping opportunity.
Many have commented before on the state of the licensing aspect of Java, which places “Field of Use” restrictions on where alternate implementors can run their JDKS. This was instigated by Sun in order to prevent open and separate implementations for running on the early 2000 era “dumbphones”, which was their only significant licensing stream for Java.
The Apache Harmony project aimed to provide an independent implementation not only of the JVM but also the class libraries, but without being allowed access to the Java TCK was never able to refer to itself as Java. Since Oracle's takeover of Sun Microsystems, it had stepped up the pressure against Apache, inviting IBM to play a key role in the future of the OpenJDK (and subsequently Apple as well) to avoid platform-specific forks.
Stephen Colebourne, who has been writing for some time about the situation, calls it passing in the Zombie JCP, highlighting “You cannot claim to be an Open Standards body if you do not allow implementations of the specification.”
In the latest round SouJava, IBM, RedHat, the London Java Community, Goldman Sachs & Co, and Fujitsu all raised concerns about licensing, and a number of participants also raised concerns about the overall transparency of the process. During the earlier review ballot everyone except Apache, Google and Tim Peierls voted for the proposal, making it the first JavaSE that wasn't unanimously voted for. However, Werner Keil, SAP AG, IBM, Eclipse, RedHat and Credit Suisse all made comments in their votes that the ongoing dispute was harmful to the Java community at large. Since Oracle was going to go ahead with the release regardless of the outcome of the vote, some members switched from abstaining to voting against the proposal in protest.
The WebSphere Liberty Profile for Developers: An Introduction
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
Good Relationships: The Spring Data Neo4J Guide Book
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
Why do you write this now? The results of the votes are known for more than 6 months.
Because he referenced the wrong vote ... should be jcp.org/en/jsr/results?id=5207
Thanks for pointing this out. We've amended the link, and edited slightly to clarify.
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