The document discusses how middleware is evolving to work with cloud computing platforms. Middleware traditionally ran on in-house data centers but is now deployed in virtualized environments, public clouds, and platforms as a service (PaaS). For middleware to effectively operate in the cloud, it needs to integrate well with cloud infrastructure, dynamically scale up and down on demand, support multi-tenancy, and have real-time monitoring and security across cloud deployments. The conclusion states that platform as a service represents the next generation of application servers for middleware in the cloud.

1. Jim Liddle January 21, 2009 Middleware as a Service How the Cloud is changing next generation middleware

2. Middleware Evolution in last 10 years CORBA J2EE JEE / Spring Today Deployed in-house or DC Deployed in-house, DC , Virtualized or public cloud

3. Convergance….or not ? Virtualization Mainstream Middleware today Distributed Data Caching Compute Grid Event Processing Application Server Messaging Data Amazon: EC2 + Hadoop +SQS +SimpleDB PaaS ex. Google App Eng. NOSQL etc On Cloud Platform Gap

4. Cloud is forcing Middleware to evolve Ability to work in virtualized environments Integrate well i.e. EC2, XEN, VMWARE etc Provisioning & Management Ability to support ‘on demand’ Support scale on demand – “elasticity” Support scale down Support this on public/private/hybrid infrastructures Ability to self-balance Support or integrate with Map / Reduce style services Setting up messaging infrastructure Plumbing services together Speed – the faster the better Latency is more important on the cloud Time costs £ Multi-tenancy Support Out of the box Simple to use Real-Time Monitoring and Management Event based support Fine Grained & Coarse grained Security End-to-end

5. Conclusion PaaS = Next Generation Application Server