Toward Nex-Generation Middleware?

A large range of application domains, from real-time embedded systems to grid-computing applications, now requires distribution. This trend implies definitions of new or tailored distribution mechanisms dedicated to specific applications and puts a strain on current middleware architectures and development. Middleware intends to separate an application from variations in hardware and operating systems. This new interoperability problem itself is serious industrial issue. We call this the middleware paradox. Next-generation middleware should be versatile enough to instantiate the exact required mechanisms of different distribution models. Middleware components that depend on a specific distribution model should be limited to application-level components or to protocol-level components.

[1]  Douglas C. Schmidt,et al.  Applying patterns to develop extensible ORB middleware , 1999, IEEE Commun. Mag..

[2]  Seán Baker A2A, B2B - now we need M2M (middleware to middleware) technology , 2001, Proceedings 3rd International Symposium on Distributed Objects and Applications.

[3]  Jean-Bernard Stefani,et al.  Jonathan: an open distributed processing environment in Java , 1999, Distributed Syst. Eng..

[4]  Dennis Gannon,et al.  Java RMI performance and object model interoperability: experiments with Java/HPC++ , 1998, Concurr. Pract. Exp..

[5]  Laurent Pautet,et al.  On the Formal Verification of Middleware Behavioral Properties , 2005, Electron. Notes Theor. Comput. Sci..

[6]  Dennis Gannon,et al.  Java RMI performance and object model interoperability: experiments with Java/HPC++ , 1998 .

[7]  Roy H. Campbell,et al.  Quarterware for middleware , 1998, Proceedings. 18th International Conference on Distributed Computing Systems (Cat. No.98CB36183).