Various cloud applications can be regarded as the supportiveassociations between the general application resources and application-specific software components, such as JVMs (Java Virtual Machines), application servers, database servers, cloud web service and the additional transaction processing tools. As these tools appear to be lying below the applications but “above” the standard OS, they are often known as the “middleware”.
The IaaS deployments may bind the middleware components to the applications in the form of 1:1, even in the event where they are deployed in the different VMs (Virtual Machines). This can augment the amount of VMs while reducing the utilization and efficiency in the cloud and eroding the business case. Virtualizing middleware can be the right solution to this.
Like several other concepts in IT today, middleware virtualization also has an expanding and cloudy definition. Also, the issues pertaining to middleware deployment in cloud and virtual environments are broad. This post shares an insight about how the middleware virtualization is taking place. A software and cloud architect must understand the basic issues related to middleware virtualization, look out for the illustrative tools in every category and comprehend where the application’s growth will take their middleware requisites.
Most of the middleware in today’s IT scenario is based on Java, which needs the JVM deployment on the application deployment and VMs within the JVMs. Most of the middleware virtualization discussions typically revolve across the middleware model hosted by Java leveraged by few of the initial cloudapplications – database servers, application servers and a Web server. This model may be hugely wasteful in the cloud due to the middleware replication.
Virtualizing Java might appear as a logical approach and that is actually another direction which the market is taking. But, a programming language like Java in its original form is not multi-tenant and this is what the problem is. One has to find out ways to deal with this.