In his keynote at VMworld last week, VMware CTO Steve Herrod showed a very interesting project called AppBlast. According to this news release thereafter, “Project AppBlast will provide the universal delivery of any application, including Windows-based applications, to any device supporting HTML5, enabling instant remote access to applications without the heavy footprint of the underlying operating system.”
One challenge almost every ISV faces today is how to quickly get “cloudy” with least investment. From business side, SaaS is a new model for most ISVs, meaning it’s still hard to project revenue. Even worse, the SaaS service may cut into the license revenue of existing product. Technically, it may require a full re-design and re-implementation of product for maximum multi-tenancy. Putting together, it’s a big challenge for decision makers.
But it doesn’t have to be difficult with a right strategy. This post explains how to support SaaS without re-designing existing applications, which means a big saving for the ISVs.
Most people who are interested in VMworld already know the public voting for the proposal is now open till 26th. If you would like to hear about specific topics, it’s high time to cast your votes.
For each track, all the presentation proposals are listed together in one page. To quickly locate a particular proposal, you can use find feature of your browser. Once you login, I would suggest to browse all the proposals and vote for those you find useful. Casting a vote is just two mouse clicks: one for voting and the other to close the confirmation message box.
With the growth of virtualization, a new term “virtual appliance” has been coined for a special type of virtual machines that are used like applications. What does it really mean?
First, a virtual appliance is still a virtual machine. When seen in vSphere Client, the virtual appliance does not look much different from other typical virtual machines. Secondly, the functionality of the virtual machine is limited to that of an application. More often than not, the virtual machine is installed with one application. Because of this, the underlying OS is stripped down only to the minimum required to support that application. This type of OS is also called Just Enough OS (JEOS). All the existence of the JEOS is to support the application in the virtual appliance.
Now, is it a VM or an application? It could be either, depending how you look at it. For ESX/vCenter, a virtual appliance is a virtual machine. You can manage it just like any other virtual machine. For application users, it’s an application, a special one that is different from a normal application.
“Develop Once, Run Everywhere”
Adobe Flex has done a fairly good job for Web. Even better the same code can be easily tweaked to run as a standalone application with Adobe AIR. This was once an expectation for Java when it first came out to run as an Applet. Somehow it didn’t succeed in its birth place, but gained its ground at the server side instead.
JavaFX from Sun is a nice try but too late in the game. More importantly, Sun is not a client software company like Microsoft who was also late with SliverLight but has client side expertise and managed to compete. I don’t think Sun will reclaim its already lost client market at all, and therefore JavaFX is likely a candidate to be axed after Oracle’s acquisition. The investment on JavaFX should have gone to Java Swing, which is a lackluster compared with IBM SWT.