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 Charles Humble on Sep 21, 2011
ZeroTurnaround today released JRebel 4.5 and announced JRebel Social, a beta version of their popular "redeploy killer" that is free for non-commercial use, provided you are willing to give ZeroTurnaround access to your social network.
JRebel, which can be thought of as a more extensive Hotswap, allows Java developers to instantly see any code change they make, without the need to build or redeploy the application. A previous InfoQ article provides many of the technical details.
According to today's announcement, the 4.5 release includes support for:
JRebel is available as a yearly subscription, starting at US$265 per developer, per year for the Base edition. The company also offers an Enterprise edition, which includes a License Server that supports "floating" licenses and management reporting for larger teams. Premium Support for teams of 10 and larger is also available.
JRebel Social, currently offered in beta, is free to use for non-commercial projects. It requires you to allow ZeroTurnaround to use your Facebook or Twitter account to let everyone know how much time you've saved. David Booth, CEO of ZeroTurnaround, told us
Once a month, through Facebook or Twitter, we'll make a post that says, "This month I saved x hours, eliminated Y redeploys using JRebel Social for free." In return for that little bit of access to someone's social network, and the caveat that you are not using it on commercial products, we thought everyone should be able to use JRebel.
Of course, since you are giving ZeroTurnaround access to your social network there is an element of trust here. In the case of the Twitter version, for example, you specifically authorise ZeroTurnaround to:
This said, Booth did stress to InfoQ on the phone that ZeroTurnaround has no plans to access user information from the social sites as they're not interested in data collection, and are too busy anyway for that type of work.
The decision to offer a free version of the product is quite bold. ZeroTurnaround started life within another company called Webmedia. They went from a 2 person team at the beginning of 2008 to their current size of around 30 people, seeing annual growth of 200-300% over the last 3 years. In July of this year Bain Capital Ventures bought out Webmedia Group's ownership of the company, though ZeroTurnaround isn't Venture Capital funded, surviving entirely off their JRebel revenue.
The firm has received a large number of awards this year, including a Jolt Productivity Award, JAX 2011 Most Innovative Java Technology, and Estonian Innovation 2011.
The WebSphere Liberty Profile for Developers: An Introduction
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
Introduction to WebSphere Liberty Profile
Big Data, Cloud & Mobile: Navigate the New Development Reality with Resources from IBM
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
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