Visual WebGui: Cloud Optimization and the Application Layer

DZone 's Guide to

Visual WebGui: Cloud Optimization and the Application Layer

· Cloud Zone ·
Free Resource

Various cloud infrastructures lack a cross-cloud application platform. Cloud providers have invested heavily in cloud infrastructure but some have left the application layer unattended.  Vendors like VMWare and Gizmox are among the few that target the application layer.  DZone conducted an exclusive interview with Gizmox marketing manager Roy Goffer about his company's Visual WebGui (VWG) web and cloud platform.  Goffer says that VWG has an architecture that is optimized for the cloud.  Gizmox recently announced support for running the VWG platform on the Windows Azure cloud.

With VWG's support for Azure deployment, developers can take the apps they've built in the Visual Studio IDE and select standard web server (IIS) deployment or Windows Azure deployment. The system will process your chosen deployment and prepare the application. The rest is standard DLL based copy/paste deployment to the Web or the cloud.  Visual WebGui can also allow legacy code to be reused by migrating it to the VWG cloud platform for cross-platform deployment on Cloud platforms such as Microsoft Windows Azure and Amazon EC2.

Copy & Paste application deployment in Visual WebGui

Roy Goffer said that VWG is designed primarily to fit the cloud architecture so it can extend its optimize applications for the cloud.  Goffer believes that cloud applications should be versatile.  According to Goffer, cross-cloud application layers should provide:

  1. A standard way to develop applications that can run on cross-cloud infrastructure and avoid vendor lock-in.
  2. A Cloud aware ace feature that allows developers to target the cloud deployment of their choice once the application is developed.
  3. Multi-tenant remote management of applications.
  4. Pre-deployment assortment & life cycle management.
  5. An added security layer to avoid data penetration through open endpoints.
These are the features provided in VWG, Goffer says.  

Gil Mor, the VP of business development at Gizmox, said, "A Visual WebGui application is highly optimized to reduce bandwidth and CPU requirements.  So it is especially well suited to a cloud computing platform, where the customer is charged based on usage."

Goffer explains how VWG optimizes its applicaitons with its unique architecture.  "VWG runs its application on the cloud servers directly with no intermediate layer.  It integrates with the data base natively.  Data never leaves the server vault as VWG does not transfer data or logic to the client."  VWG virtualizes the application on the server and then screens its UI on a standard browser.   VWG runs with a standard HTTP/XML using meta-data.  The meta-data is in the form of events from the client (user interaction) and update commands from the server.  "With this, VWG achieves a responsive run time which consumes 50% of traditional web CPU and 10% of bandwidth," said Goffer.  "This architecture is the cloud architecture and the fit makes VWG unique."

Wave Maker, SpringSource, and others are currently working on cloud platforms similar to Gizmox's.  Goffer said that these products will not compete directly because VWG's strategy is to offer existing standards compatibility.  The other offerings might be good for developers who want to work with the tools and standards of a particular platform like SpringSource.

Goffer says Gizmox is working on supporting point and click deployment for more clouds.  "We expect that by the 2nd Quarter of 2010, the full featured offering will be shipped out.  VWG is also planning to offer simple comet (real time capabilities), Mash up, and other features that are made possible by its runtime."  Goffer also says that we can expect Gizmox to keep enhancing its migration capabilities.  "All in all, migrating and updating a local installed application into the cloud quickly and simply without web or cloud compromises is where VWG shines," said Goffer.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}