Skip to main content

Application Virtualization tutorials



Nice articles on Application Virtualization. Martin Brown explains:

You can consider a grid to be a form of virtualization -- if you consider the individual components and functionality within your grid as virtualized components that can be accessed by higher-level applications. For example, within a typical grid environment, the security of the grid, storage methods (particularly for resources and persistent, but transient, data used during grid execution), and the entire method of executing the application are abstracted.

The grid infrastructure sits on top of one or more platforms and provides services within a standardized environment. You can almost consider the environment to be a new operating system and platform. Effectively, the underlying platforms (hardware and OS) are hidden by the grid environment. The grid then provides a new environment for the execution of applications, and the application runs in this virtualized environment. In this respect, your application runs in a virtualized environment created by the grid, which in turn creates the virtualized environment by collectively organizing the grid components to operate as a single resource.

In this series, we will examine the three levels -- grid infrastructure, grid environment and grid applications -- and how they interact, and how to build and adapt your applications using the standardized environment offered by the grid and the solutions offered by the Open Grid Services Architecture (OGSA), service-oriented architecture (SOA), the Web services (WS) standards, and other techniques.



Here check them out part 1, part 2 and part 3.
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...
Post a Comment
Read more